@eforge-build/input
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.7.21 | 3 / 3 | |
| 0.7.20 | 3 / 3 | |
| 0.7.12 | 3 / 3 | |
| 0.7.11 | 3 / 3 | |
| 0.7.10 | 3 / 3 | |
| 0.7.9 | 3 / 3 |
v0.7.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.