← Home

@spectrum-css/picker

npm Repository Homepage
9
Versions
—
License
No
Install Scripts
Missing
Provenance

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.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Adobe org maintainer rotation on established monorepo; no accompanying malicious behavior. ai
source-diff source-size-tripled AI (source-diff): Dist CSS build output growth for a CSS component package, not injected payload. ai
maintainer-change maintainer-added AI (maintainer-change): Normal maintainer rotation within Adobe's spectrum-css monorepo team. ai

Versions (showing 9 of 9)

Version Deps Published
9.2.0 0 / 7
9.1.4 0 / 7
9.1.3 0 / 7
9.1.2 0 / 7
9.1.1 0 / 7
9.1.0 0 / 7
9.0.1 0 / 11
9.0.0 0 / 11
1.0.1 0 / 7

v9.1.4

2 findings
MEDIUM Publisher changed: garthdb → castastrophe (on 2025-03-10, unremoved on npm for 494d) provenance

This version was published by a different npm account (castastrophe) than the most recent previously approved version (garthdb) on 2025-03-10. It has since remained available on npm for 494 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.

v9.1.3

2 findings
MEDIUM Publisher changed: garthdb → patrickfulton (on 2025-03-04, unremoved on npm for 500d) provenance

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

LOW No provenance attestation provenance

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

v9.1.2

2 findings
MEDIUM Publisher changed: garthdb → patrickfulton (on 2025-02-27, unremoved on npm for 505d) provenance

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

LOW No provenance attestation provenance

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

v9.1.1

2 findings
MEDIUM Publisher changed: garthdb → patrickfulton (on 2025-02-20, unremoved on npm for 512d) provenance

This version was published by a different npm account (patrickfulton) than the most recent previously approved version (garthdb) on 2025-02-20. It has since remained available on npm for 512 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.

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

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

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