@spectrum-css/link
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): Known Adobe org maintainer rotation across the spectrum-css monorepo. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Same rotation; not a takeover pattern given long stable availability. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Publisher change stable 532d on npm, inconsistent with compromise. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Monorepo package with sparse per-component releases; not anomalous. | ai | |
| typosquat | typosquat.levenshtein:pino | AI (typosquat): Scoped Adobe Spectrum CSS package; no relation to pino. Levenshtein match is coincidental. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 7.2.0 | 0 / 1 | |
| 7.1.0 | 0 / 1 | |
| 7.0.1 | 0 / 5 | |
| 7.0.0 | 0 / 5 | |
| 3.1.1 | 0 / 3 |
v7.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.
v7.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.
v7.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.