@spectrum-css/actiongroup
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legitimate Adobe org maintainer transition; publisher has strong track record. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with maintainer rotation, not takeover. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Long-stable publish (528d), inconsistent with account compromise. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Small CSS component package; dist size growth is normal, not payload injection. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Adobe monorepo maintainer rotation, publisher stable on npm long-term. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 6.2.0 | 0 / 2 | |
| 6.1.0 | 0 / 2 | |
| 6.0.1 | 0 / 6 | |
| 6.0.0 | 0 / 6 | |
| 1.0.1 | 0 / 5 |
v6.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.
v6.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.
v6.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.