@toptal/picasso-list
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Package has SLSA provenance attestation; missing gitHead reflects CI pipeline change, not a supply chain risk. | ai | |
| phantom-deps | phantom-dep:classnames | AI (phantom-deps): classnames is a declared runtime dependency; phantom-dep fires as false positive for this package. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 5.0.23 | 6 / 3 | |
| 5.0.22 | 6 / 3 | |
| 5.0.21 | 6 / 3 | |
| 5.0.20 | 6 / 3 | |
| 5.0.19 | 6 / 3 | |
| 5.0.18 | 6 / 3 | |
| 5.0.17 | 6 / 3 | |
| 5.0.16 | 6 / 3 | |
| 5.0.15 | 6 / 3 | |
| 5.0.14 | 6 / 3 | |
| 5.0.13 | 6 / 3 | |
| 5.0.12 | 6 / 3 | |
| 5.0.11 | 6 / 3 | |
| 5.0.10 | 6 / 3 | |
| 5.0.9 | 6 / 3 | |
| 5.0.8 | 6 / 3 | |
| 5.0.7 | 6 / 3 | |
| 5.0.6 | 6 / 3 | |
| 5.0.5 | 6 / 3 | |
| 5.0.4 | 6 / 3 | |
| 5.0.3 | 6 / 3 | |
| 5.0.2 | 6 / 3 | |
| 5.0.1 | 6 / 3 | |
| 5.0.0 | 6 / 3 |
v5.0.23
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
v5.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.