@toptal/picasso-empty-state
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 superseded by Sigstore-backed CI/CD attestation for this package. | ai | |
| provenance | no-provenance | AI (provenance): Toptal's picasso monorepo consistently publishes without Sigstore provenance; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@toptal/picasso-icons | AI (dependencies): Internal monorepo dependency from the same Toptal/picasso org; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@toptal/picasso-container | AI (dependencies): Internal monorepo dependency from the same Toptal/picasso org; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@toptal/picasso-typography | AI (dependencies): Internal monorepo dependency from the same Toptal/picasso org; stable false positive for this package family. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 2.0.25 | 3 / 0 | |
| 2.0.24 | 3 / 0 | |
| 2.0.23 | 3 / 0 | |
| 2.0.22 | 3 / 0 | |
| 2.0.21 | 3 / 0 | |
| 2.0.20 | 3 / 0 | |
| 2.0.19 | 3 / 0 | |
| 2.0.18 | 3 / 0 | |
| 2.0.17 | 3 / 0 | |
| 2.0.16 | 3 / 0 | |
| 2.0.15 | 3 / 0 | |
| 2.0.14 | 3 / 0 | |
| 2.0.13 | 3 / 0 | |
| 2.0.12 | 3 / 0 | |
| 2.0.11 | 3 / 0 | |
| 2.0.10 | 3 / 0 | |
| 2.0.9 | 3 / 0 | |
| 2.0.8 | 3 / 0 | |
| 2.0.7 | 3 / 0 | |
| 2.0.6 | 3 / 0 | |
| 2.0.5 | 3 / 0 | |
| 2.0.4 | 3 / 0 | |
| 2.0.3 | 3 / 0 | |
| 2.0.2 | 3 / 0 | |
| 2.0.1 | 3 / 0 | |
| 2.0.0 | 3 / 0 |
v2.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.