@soybeanjs/utils
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.1.1 | 0 / 10 | |
| 0.1.0 | 0 / 10 | |
| 0.0.5 | 0 / 10 | |
| 0.0.4 | 0 / 9 | |
| 0.0.3 | 0 / 9 | |
| 0.0.2 | 0 / 9 | |
| 0.0.1 | 0 / 9 |
v0.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.