@propellerads/icon
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:@propellerads/theme-annotation | AI (phantom-deps): Same-org scoped package; phantom-dep heuristic is unreliable for peer/style deps in monorepos. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 7.2.1 | 2 / 6 | |
| 7.2.0 | 1 / 6 | |
| 7.1.1 | 1 / 6 | |
| 7.1.0 | 1 / 6 | |
| 7.0.0 | 1 / 7 | |
| 6.0.2 | 1 / 5 |
v7.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.