@toptal/picasso-note
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): SLSA provenance attestation present; gitHead absence is superseded by stronger Sigstore-backed supply chain integrity. | ai | |
| phantom-deps | phantom-dep:classnames | AI (phantom-deps): classnames is declared in dependencies; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 4.0.9 | 4 / 1 | |
| 4.0.8 | 4 / 1 | |
| 4.0.7 | 4 / 1 | |
| 4.0.6 | 4 / 1 | |
| 4.0.5 | 4 / 1 | |
| 4.0.4 | 4 / 1 | |
| 4.0.3 | 4 / 1 | |
| 4.0.2 | 4 / 1 | |
| 4.0.1 | 4 / 1 | |
| 4.0.0 | 4 / 1 |
v4.0.9
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.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.