@spectrum-css/divider
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 |
|---|---|---|---|---|
| source-diff | source-size-tripled | AI (source-diff): Tiny CSS component; absolute size negligible, growth is normal content change. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Known Adobe Spectrum CSS team rotation, long-stable on npm. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Monorepo component with irregular per-package publish cadence, not a takeover indicator here. | ai | |
| phantom-deps | phantom-dep:@spectrum-css/vars | AI (phantom-deps): CSS component in Adobe monorepo; @spectrum-css/vars is a CSS variable dependency, not a JS import — phantom-dep is a stable false positive here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): CSS-only component package; no code blocks or keywords expected in README. Not spam. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 5.2.0 | 0 / 1 | |
| 5.1.0 | 0 / 1 | |
| 5.0.1 | 0 / 5 | |
| 5.0.0 | 0 / 5 | |
| 1.0.3 | 1 / 5 |
v5.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.
v5.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.
v5.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.