@pie-players/pie-tool-color-scheme
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:daisyui | AI (phantom-deps): Declared dependency used in build/config; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@pie-players/pie-context | AI (phantom-deps): Monorepo internal dep; declared and used via build/exports. | ai | |
| phantom-deps | phantom-dep:@pie-players/pie-players-shared | AI (phantom-deps): Monorepo internal dep; declared and used via build/exports. | ai | |
| phantom-deps | phantom-dep:@pie-players/pie-assessment-toolkit | AI (phantom-deps): Monorepo internal dep; declared and used via build/exports. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.1.9 | 4 / 6 | |
| 0.1.8 | 4 / 6 | |
| 0.1.6 | 4 / 6 | |
| 0.1.5 | 2 / 6 | |
| 0.1.4 | 2 / 6 | |
| 0.1.3 | 2 / 6 | |
| 0.1.2 | 2 / 6 | |
| 0.1.1 | 2 / 6 |
v0.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.