@pie-players/pie-fixed-player
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
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): CSS framework used in styling; typical for component libraries to declare but not directly import. | ai | |
| phantom-deps | phantom-dep:@pie-players/pie-theme | AI (phantom-deps): Same-org internal dependency; re-exported for consumers; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@pie-players/pie-players-shared | AI (phantom-deps): Same-org internal dependency; re-exported for consumers; stable pattern for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.2.5 | 3 / 8 | |
| 0.2.4 | 3 / 8 | |
| 0.2.2 | 1 / 8 | |
| 0.2.1 | 1 / 8 | |
| 0.2.0 | 1 / 8 |
v0.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.