@toptal/picasso-drawer
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 | no-provenance | AI (provenance): Common for npm packages; not a security blocker for established libraries. | ai | |
| provenance | missing-githead | AI (provenance): SLSA provenance attestation present; gitHead absence is benign given CI/CD publish with Sigstore attestation. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Established Toptal monorepo component with SLSA provenance; dormancy explained by normal release cadence gaps. | ai | |
| dependencies | unvetted-dep:@toptal/picasso-slide | AI (dependencies): Internal sibling package from the same Toptal picasso monorepo. | ai | |
| dependencies | unvetted-dep:@toptal/picasso-utils | AI (dependencies): Internal sibling package from the same Toptal picasso monorepo. | ai | |
| dependencies | unvetted-dep:@toptal/picasso-button | AI (dependencies): Internal sibling package from the same Toptal picasso monorepo. | ai | |
| dependencies | unvetted-dep:@toptal/picasso-backdrop | AI (dependencies): Internal sibling package from the same Toptal picasso monorepo. | ai | |
| dependencies | unvetted-dep:@mui/base | AI (dependencies): Well-known MUI base package; stable dependency for this UI component library. | ai | |
| dependencies | unvetted-dep:@toptal/picasso-typography | AI (dependencies): Internal sibling package from the same Toptal picasso monorepo. | ai | |
| dependencies | unvetted-peer-dep:@toptal/picasso-provider | AI (dependencies): Internal sibling peer dep from the same Toptal picasso monorepo. | ai | |
| dependencies | unvetted-peer-dep:@toptal/picasso-tailwind-merge | AI (dependencies): Internal sibling peer dep from the same Toptal picasso monorepo. | ai | |
| dependencies | unvetted-dep:@toptal/picasso-container | AI (dependencies): Internal sibling package from the same Toptal picasso monorepo. | ai | |
| dependencies | unvetted-dep:@toptal/picasso-icons | AI (dependencies): Internal sibling package from the same Toptal picasso monorepo. | ai | |
| dependencies | unvetted-dep:@toptal/picasso-paper | AI (dependencies): Internal sibling package from the same Toptal picasso monorepo. | ai |
Versions (showing 48 of 48)
| Version | Deps | Published |
|---|---|---|
| 3.0.47 | 9 / 2 | |
| 3.0.46 | 9 / 2 | |
| 3.0.45 | 9 / 2 | |
| 3.0.44 | 9 / 2 | |
| 3.0.43 | 9 / 2 | |
| 3.0.42 | 9 / 2 | |
| 3.0.41 | 9 / 2 | |
| 3.0.40 | 9 / 2 | |
| 3.0.39 | 9 / 2 | |
| 3.0.38 | 9 / 2 | |
| 3.0.37 | 9 / 2 | |
| 3.0.36 | 9 / 2 | |
| 3.0.35 | 9 / 2 | |
| 3.0.34 | 9 / 2 | |
| 3.0.33 | 10 / 1 | |
| 3.0.32 | 10 / 1 | |
| 3.0.31 | 10 / 1 | |
| 3.0.30 | 10 / 1 | |
| 3.0.29 | 10 / 1 | |
| 3.0.28 | 10 / 1 | |
| 3.0.27 | 10 / 1 | |
| 3.0.26 | 10 / 1 | |
| 3.0.25 | 10 / 1 | |
| 3.0.24 | 10 / 1 | |
| 3.0.23 | 10 / 1 | |
| 3.0.22 | 10 / 1 | |
| 3.0.21 | 10 / 1 | |
| 3.0.20 | 10 / 1 | |
| 3.0.19 | 10 / 1 | |
| 3.0.18 | 10 / 1 | |
| 3.0.17 | 10 / 1 | |
| 3.0.16 | 10 / 1 | |
| 3.0.15 | 10 / 1 | |
| 3.0.14 | 10 / 1 | |
| 3.0.13 | 10 / 1 | |
| 3.0.12 | 10 / 1 | |
| 3.0.11 | 10 / 1 | |
| 3.0.10 | 10 / 1 | |
| 3.0.9 | 10 / 1 | |
| 3.0.8 | 10 / 1 | |
| 3.0.7 | 10 / 1 | |
| 3.0.6 | 10 / 1 | |
| 3.0.5 | 10 / 1 | |
| 3.0.4 | 10 / 1 | |
| 3.0.3 | 10 / 1 | |
| 3.0.2 | 10 / 1 | |
| 3.0.1 | 10 / 1 | |
| 3.0.0 | 10 / 1 |
v3.0.47
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This 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.
v3.0.39
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.36
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (talbot) on 2025-09-18, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v3.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.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.
v3.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.