@spectrum-css/underlay — Greenflagged

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

garthdbjianliao79patrickfultoncastastrophe

Keywords

design-systemspectrumspectrum-cssadobeadobe-spectrumcomponentcss

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): Adobe org maintainer rotation, long-tenured monorepo package.	ai	2026/07/18
maintainer-change	maintainer-removed	AI (maintainer-change): Expected with maintainer rotation, not a takeover pattern.	ai	2026/07/18
provenance	publisher-changed-stale	AI (provenance): Stable 532d on npm, consistent with legitimate transfer.	ai	2026/07/18
source-diff	source-size-tripled	AI (source-diff): Trivial absolute size change (61B->2KB) for tiny CSS package.	ai	2026/07/18
publish-pattern	dormant-publish	AI (publish-pattern): Long-lived Adobe design system component; dormancy reflects upstream release cadence, not takeover.	ai	2026/05/20

Versions (showing 6 of 6)

Version	Deps	Published
6.2.0	0 / 2	2025-09-15
6.1.1	0 / 2	2025-07-30
6.1.0	0 / 2	2025-02-12
6.0.1	0 / 6	2025-02-04
6.0.0	0 / 6	2025-01-31
2.0.9	0 / 3	2021-03-10

v6.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.1.0

2 findings

MEDIUM Publisher changed: garthdb → patrickfulton (on 2025-02-12, unremoved on npm for 520d) provenance

This 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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.0.1

2 findings

MEDIUM Publisher changed: garthdb → patrickfulton (on 2025-02-04, unremoved on npm for 528d) provenance

This 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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.0.0

2 findings

MEDIUM Publisher changed: garthdb → patrickfulton (on 2025-01-31, unremoved on npm for 532d) provenance

This 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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.