@toptal/picasso-dropzone
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@toptal/picasso-form | AI (dependencies): Internal sibling dep from same Toptal/picasso monorepo; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@toptal/picasso-icons | AI (dependencies): Internal sibling dep from same Toptal/picasso monorepo; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@toptal/picasso-utils | AI (dependencies): Internal sibling dep from same Toptal/picasso monorepo; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@toptal/picasso-container | AI (dependencies): Internal sibling dep from same Toptal/picasso monorepo; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@toptal/picasso-file-input | AI (dependencies): Internal sibling dep from same Toptal/picasso monorepo; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@toptal/picasso-typography | AI (dependencies): Internal sibling dep from same Toptal/picasso monorepo; stable pattern across all versions. | ai | |
| phantom-deps | phantom-dep:classnames | AI (phantom-deps): classnames is a declared runtime dep; phantom-dep false positive for this package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 5.0.34 | 8 / 1 | |
| 5.0.33 | 8 / 1 | |
| 5.0.32 | 8 / 1 | |
| 5.0.31 | 8 / 1 | |
| 5.0.30 | 8 / 1 | |
| 5.0.29 | 8 / 1 | |
| 5.0.28 | 8 / 1 | |
| 5.0.25 | 8 / 1 | |
| 5.0.24 | 8 / 1 | |
| 5.0.23 | 8 / 1 | |
| 5.0.22 | 8 / 1 | |
| 5.0.21 | 8 / 1 |
v5.0.34
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.33
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.32
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.31
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.30
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.29
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.28
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.25
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.