@spectrum-css/statuslight
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 org maintainer rotation within Adobe's spectrum-css monorepo. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Prior maintainer rotation, not a takeover; publisher stable 532d. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Long-stable publish inconsistent with account takeover. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 9.2.0 | 0 / 1 | |
| 9.1.0 | 0 / 1 | |
| 9.0.1 | 0 / 5 | |
| 9.0.0 | 0 / 5 | |
| 3.0.2 | 0 / 3 |
v9.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.
v9.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.
v9.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.