spec-change
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.11.21 | 6 / 7 | |
| 1.11.20 | 6 / 7 | |
| 1.11.19 | 6 / 7 | |
| 1.11.18 | 6 / 7 | |
| 1.11.17 | 6 / 7 | |
| 1.11.16 | 6 / 7 | |
| 1.11.15 | 6 / 7 | |
| 1.11.14 | 6 / 7 | |
| 1.11.13 | 6 / 7 | |
| 1.11.12 | 6 / 7 | |
| 1.11.11 | 6 / 7 | |
| 1.11.10 | 6 / 7 | |
| 1.11.9 | 6 / 7 | |
| 1.11.8 | 6 / 7 | |
| 1.11.7 | 6 / 7 | |
| 1.11.6 | 6 / 7 | |
| 1.11.5 | 6 / 7 |
v1.11.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.11.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.