@spectrum-css/radio
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Normal maintainer rotation within Adobe's official spectrum-css org. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Team rotation, not a takeover indicator, given package's long clean history. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Tiny CSS dist file growth (61B to 7KB), not a payload signal. | ai | |
| typosquat | typosquat.levenshtein:redis | AI (typosquat): Adobe Spectrum CSS scoped package; Levenshtein match to 'redis' is coincidental and not a typosquat. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 10.2.0 | 0 / 2 | |
| 10.1.1 | 0 / 2 | |
| 10.1.0 | 0 / 2 | |
| 10.0.1 | 0 / 6 | |
| 10.0.0 | 0 / 6 | |
| 3.0.2 | 0 / 4 |
v10.1.0
2 findingsThis version was published by a different npm account (patrickfulton) than the most recent previously approved version (garthdb) on 2025-02-12. It has since remained available on npm for 520 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.1
2 findingsThis version was published by a different npm account (patrickfulton) than the most recent previously approved version (garthdb) on 2025-02-04. It has since remained available on npm for 528 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.0
2 findingsThis version was published by a different npm account (patrickfulton) than the most recent previously approved version (garthdb) on 2025-01-31. It has since remained available on npm for 532 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.