@toptal/picasso-tree-view
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 cosmetic given CI/CD publish with Sigstore attestation. | ai | |
| provenance | publisher-changed | AI (provenance): Toptal migrated publishing to GitHub Actions CI/CD; SLSA provenance attestation confirms legitimate automated pipeline. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Established Toptal monorepo component with SLSA provenance; inactivity gap is not indicative of takeover given CI/CD publishing and clean diff. | ai | |
| dependencies | unvetted-dep:@toptal/picasso-utils | AI (dependencies): Same-org monorepo sibling dependency; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@toptal/picasso-button | AI (dependencies): Same-org monorepo sibling dependency; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@toptal/picasso-container | AI (dependencies): Same-org monorepo sibling dependency; stable false positive for this package. | ai |
Versions (showing 48 of 48)
| Version | Deps | Published |
|---|---|---|
| 3.0.47 | 4 / 1 | |
| 3.0.46 | 4 / 1 | |
| 3.0.45 | 4 / 1 | |
| 3.0.44 | 4 / 1 | |
| 3.0.43 | 4 / 1 | |
| 3.0.42 | 4 / 1 | |
| 3.0.41 | 4 / 1 | |
| 3.0.40 | 4 / 1 | |
| 3.0.39 | 4 / 1 | |
| 3.0.38 | 4 / 1 | |
| 3.0.37 | 4 / 1 | |
| 3.0.36 | 4 / 1 | |
| 3.0.35 | 4 / 1 | |
| 3.0.34 | 4 / 1 | |
| 3.0.33 | 4 / 1 | |
| 3.0.32 | 4 / 1 | |
| 3.0.31 | 4 / 1 | |
| 3.0.30 | 4 / 1 | |
| 3.0.29 | 4 / 1 | |
| 3.0.28 | 4 / 1 | |
| 3.0.27 | 4 / 1 | |
| 3.0.26 | 4 / 1 | |
| 3.0.25 | 4 / 1 | |
| 3.0.24 | 4 / 1 | |
| 3.0.23 | 4 / 1 | |
| 3.0.22 | 4 / 1 | |
| 3.0.21 | 4 / 1 | |
| 3.0.20 | 4 / 1 | |
| 3.0.19 | 4 / 1 | |
| 3.0.18 | 4 / 1 | |
| 3.0.17 | 4 / 1 | |
| 3.0.16 | 4 / 1 | |
| 3.0.15 | 4 / 1 | |
| 3.0.14 | 4 / 1 | |
| 3.0.13 | 4 / 1 | |
| 3.0.12 | 4 / 1 | |
| 3.0.11 | 4 / 1 | |
| 3.0.10 | 4 / 1 | |
| 3.0.9 | 4 / 1 | |
| 3.0.8 | 4 / 1 | |
| 3.0.7 | 4 / 1 | |
| 3.0.6 | 4 / 1 | |
| 3.0.5 | 4 / 1 | |
| 3.0.4 | 4 / 1 | |
| 3.0.3 | 4 / 1 | |
| 3.0.2 | 4 / 1 | |
| 3.0.1 | 4 / 1 | |
| 3.0.0 | 4 / 1 |
v3.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.