@donmahallem/turbo
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 3.2.63 | 0 / 5 | |
| 3.2.58 | 0 / 5 | |
| 3.2.56 | 0 / 5 | |
| 3.2.51 | 0 / 5 | |
| 3.2.44 | 0 / 5 | |
| 3.2.39 | 0 / 5 | |
| 3.2.36 | 0 / 5 | |
| 3.2.35 | 0 / 5 | |
| 3.2.34 | 0 / 5 | |
| 3.2.32 | 0 / 5 | |
| 3.2.31 | 0 / 5 | |
| 3.2.30 | 0 / 5 | |
| 3.2.27 | 0 / 5 | |
| 3.2.26 | 0 / 5 | |
| 3.2.25 | 0 / 5 | |
| 3.2.22 | 0 / 5 | |
| 3.2.1 | 0 / 5 | |
| 3.2.0 | 0 / 5 | |
| 3.1.1 | 0 / 5 | |
| 3.1.0 | 0 / 5 | |
| 3.0.1 | 0 / 5 | |
| 3.0.0 | 0 / 5 |
v3.2.63
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.