@toptal/picasso-quote
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 cosmetic given CI/CD publish with Sigstore attestation. | ai | |
| provenance | no-provenance | AI (provenance): Toptal Picasso monorepo consistently publishes without Sigstore provenance; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@toptal/picasso-container | AI (dependencies): Same-org monorepo sibling; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@toptal/picasso-typography | AI (dependencies): Same-org monorepo sibling; stable false positive for this package family. | ai |
v2.0.10
2 findingsThis 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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.