@toptal/picasso-application-update-notification
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 benign given CI/CD publish with Sigstore attestation. | ai | |
| dependencies | unvetted-dep:@toptal/picasso-icons | AI (dependencies): Internal @toptal monorepo sibling dependency; consistent pattern across all picasso packages. | ai | |
| dependencies | unvetted-dep:@toptal/picasso-container | AI (dependencies): Internal @toptal monorepo sibling dependency; consistent pattern across all picasso packages. | ai | |
| dependencies | unvetted-dep:@toptal/picasso-typography | AI (dependencies): Internal @toptal monorepo sibling dependency; consistent pattern across all picasso packages. | ai | |
| phantom-deps | phantom-dep:classnames | AI (phantom-deps): classnames is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@toptal/picasso-utils | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic false positive for monorepo packages. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 2.0.45 | 6 / 1 | |
| 2.0.44 | 6 / 1 | |
| 2.0.43 | 6 / 1 | |
| 2.0.42 | 6 / 1 | |
| 2.0.41 | 6 / 1 | |
| 2.0.40 | 6 / 1 | |
| 2.0.39 | 6 / 1 | |
| 2.0.38 | 6 / 1 | |
| 2.0.37 | 6 / 1 | |
| 2.0.36 | 6 / 1 | |
| 2.0.35 | 6 / 1 | |
| 2.0.34 | 6 / 1 | |
| 2.0.33 | 6 / 1 |
v2.0.45
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.44
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.43
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.42
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.41
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.40
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.39
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.38
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.37
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.36
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.35
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.