@spectrum-css/stepper
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 maintainer transition on official monorepo package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Org-internal maintainer rotation on long-running Adobe monorepo package. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Stable on npm for 532+ days, inconsistent with takeover per rule's own heuristic. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Baseline was near-empty (61B); growth reflects normal built CSS, not injected payload. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 7.2.0 | 0 / 5 | |
| 7.1.3 | 0 / 5 | |
| 7.1.2 | 0 / 5 | |
| 7.1.1 | 0 / 5 | |
| 7.1.0 | 0 / 5 | |
| 7.0.1 | 0 / 9 | |
| 7.0.0 | 0 / 9 | |
| 3.0.3 | 0 / 6 |
v7.1.3
2 findingsThis version was published by a different npm account (patrickfulton) than the most recent previously approved version (garthdb) on 2025-03-14. It has since remained available on npm for 490 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.1.2
2 findingsThis version was published by a different npm account (patrickfulton) than the most recent previously approved version (garthdb) on 2025-03-04. It has since remained available on npm for 500 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.1.1
2 findingsThis version was published by a different npm account (patrickfulton) than the most recent previously approved version (garthdb) on 2025-02-27. It has since remained available on npm for 505 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.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.