@propellerads/radio-group
 
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@propellerads/smart-tooltip | AI (dependencies): Internal org dependency from same propellerads namespace; consistent publisher identity makes this a stable false positive. | ai | |
| provenance | no-provenance | AI (provenance): Internal UI component library; provenance attestation not used across this publisher's packages. | ai | |
| phantom-deps | phantom-dep:@propellerads/theme-annotation | AI (phantom-deps): Same-org scoped package; declared as dependency, likely used transitively or in type declarations. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 5.0.1 | 4 / 6 | |
| 5.0.0 | 4 / 6 | |
| 4.0.5 | 4 / 5 | |
| 4.0.4 | 3 / 5 | |
| 4.0.3 | 3 / 5 | |
| 4.0.2 | 3 / 5 | |
| 4.0.1 | 3 / 5 | |
| 4.0.0 | 3 / 5 |
v5.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.