@prestyj/pixel
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:recast | AI (phantom-deps): Code transformation tool; recast loaded via config/plugin convention. | ai | |
| phantom-deps | phantom-dep:magicast | AI (phantom-deps): Code transformation tool; magicast loaded via config/plugin convention. | ai | |
| phantom-deps | phantom-dep:@babel/types | AI (phantom-deps): Babel framework package; loaded by convention in AST tools. | ai | |
| phantom-deps | phantom-dep:@babel/parser | AI (phantom-deps): Babel framework package; loaded by convention in AST tools. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 4.3.96 | 4 / 7 | |
| 4.3.95 | 4 / 7 | |
| 4.3.93 | 4 / 7 | |
| 4.3.83 | 1 / 4 |
v4.3.96
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.95
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.93
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.83
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.