@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 33 of 33)
| 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 | |
| 5.0.20 | 8 / 1 | |
| 5.0.19 | 8 / 1 | |
| 5.0.18 | 8 / 1 | |
| 5.0.17 | 8 / 1 | |
| 5.0.16 | 8 / 1 | |
| 5.0.15 | 8 / 1 | |
| 5.0.14 | 8 / 1 | |
| 5.0.13 | 8 / 1 | |
| 5.0.12 | 8 / 1 | |
| 5.0.11 | 8 / 1 | |
| 5.0.10 | 8 / 1 | |
| 5.0.9 | 8 / 1 | |
| 5.0.8 | 8 / 1 | |
| 5.0.7 | 8 / 1 | |
| 5.0.6 | 8 / 1 | |
| 5.0.5 | 8 / 1 | |
| 5.0.4 | 8 / 1 | |
| 5.0.3 | 8 / 1 | |
| 5.0.2 | 8 / 1 | |
| 5.0.1 | 8 / 1 | |
| 5.0.0 | 8 / 1 |
v5.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.