@hono/auth-js
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.1.1 | 0 / 7 | |
| 1.1.0 | 0 / 9 | |
| 1.0.17 | 0 / 8 | |
| 1.0.16 | 0 / 8 | |
| 1.0.15 | 0 / 8 | |
| 1.0.14 | 0 / 8 | |
| 1.0.13 | 0 / 8 | |
| 1.0.12 | 0 / 8 | |
| 1.0.11 | 0 / 8 |
v1.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.