@toptal/picasso-breadcrumbs
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 | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing with SLSA attestation; consistent with org-level CI/CD migration for the Toptal Picasso monorepo. | ai | |
| provenance | missing-githead | AI (provenance): SLSA provenance attestation present; gitHead absence is minor given strong CI/CD supply chain integrity signal. | ai | |
| dependencies | unvetted-dep:ap-style-title-case | AI (dependencies): Small, well-known utility; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:@toptal/picasso-icons | AI (dependencies): Internal Toptal Picasso sibling package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@toptal/picasso-utils | AI (dependencies): Internal Toptal Picasso sibling package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@toptal/picasso-typography | AI (dependencies): Internal Toptal Picasso sibling package; stable pattern across all versions. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 3.0.21 | 5 / 2 | |
| 3.0.20 | 5 / 2 | |
| 3.0.19 | 5 / 2 | |
| 3.0.18 | 5 / 2 | |
| 3.0.17 | 5 / 2 | |
| 3.0.16 | 5 / 2 | |
| 3.0.15 | 5 / 2 | |
| 3.0.14 | 5 / 2 | |
| 3.0.13 | 5 / 2 | |
| 3.0.12 | 5 / 2 | |
| 3.0.11 | 5 / 2 |
v3.0.21
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.
v3.0.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.17
2 findingsThis version was published by a different npm account than previous versions on 2025-11-26. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.16
2 findingsThis version was published by a different npm account than previous versions on 2025-11-26. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.