← Home

hono

npm Repository Homepage

Web framework built on Web Standards

10
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

yusukebe

Keywords

honowebapphttpapplicationframeworkroutercloudflareworkersfastlycomputedenobunlambdanodejs

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:pino AI (typosquat): Hono is a major web framework with 34.7M weekly downloads and 1591 days of history. The Levenshtein similarity to 'pino' is purely coincidental; no impersonation intent. ai
provenance no-provenance AI (provenance): Hono is a well-established package with strong ecosystem trust signals. Lack of Sigstore provenance is not a meaningful risk indicator here. ai

Versions (showing 10 of 10)

Version Deps Published
4.12.23 0 / 28
4.12.22 0 / 28
4.12.21 0 / 28
4.12.20 0 / 28
4.12.19 0 / 28
4.12.18 0 / 28
4.12.17 0 / 28
4.12.16 0 / 28
4.12.15 0 / 28
4.12.14 0 / 28

v4.12.23

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.12.22

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.12.21

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.12.20

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.12.19

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.12.18

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.12.17

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.12.16

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.12.15

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.