@hono/oauth-providers
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Expected artifact of CI/CD publish migration; provenance attestation compensates. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy coincides with publisher/tooling migration, not takeover. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established @hono scoped package; empty dist is pre-build artifact, missing metadata is cosmetic. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 0.8.6 | 0 / 5 | |
| 0.8.5 | 0 / 7 | |
| 0.8.4 | 0 / 7 | |
| 0.8.3 | 0 / 7 | |
| 0.8.2 | 0 / 6 | |
| 0.8.1 | 0 / 6 | |
| 0.8.0 | 0 / 6 | |
| 0.7.1 | 0 / 6 | |
| 0.7.0 | 0 / 8 | |
| 0.6.2 | 0 / 11 | |
| 0.6.1 | 0 / 11 | |
| 0.6.0 | 0 / 11 | |
| 0.5.1 | 0 / 11 | |
| 0.5.0 | 0 / 11 | |
| 0.4.0 | 0 / 11 | |
| 0.3.2 | 0 / 11 | |
| 0.3.1 | 0 / 11 | |
| 0.3.0 | 0 / 11 | |
| 0.2.0 | 0 / 10 | |
| 0.1.2 | 0 / 10 | |
| 0.1.1 | 0 / 10 | |
| 0.1.0 | 0 / 10 |
v0.8.6
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (yusukebe) on 2026-07-16, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.