← Home

@adobe/react-spectrum-ui

npm

Spectrum (S1) icons in React

6
Versions
Apache-2.0
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

dotenstopp-adobedylandepassdjaeggiadobehallsfullcolorcodermarbectripodgarthdblazdadobe-adminpatrickfultontrieloffshazronkrisnyedcpfsdknatebaldwindevongovettaspro83symanovidpfisterstefan-guggisbergkorrarofekptdobe

Keywords

reacticonSpectrum

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
email-domain unclaimed-email:adobeio.com AI (email-domain): adobeio.com was an Adobe internal domain; @adobe npm scope access controls prevent domain-based hijack of publish rights. ai
provenance publisher-changed AI (provenance): Publisher change from jianliao79 to garthdb in 2022 reflects legitimate Adobe team transition; both are long-standing Adobe contributors. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers are Adobe team members; corporate maintainer rotation is expected for @adobe-scoped packages. ai
maintainer-change maintainer-removed AI (maintainer-change): Removed maintainers reflect normal Adobe team rotation; no signs of hostile takeover. ai
provenance no-provenance AI (provenance): Older Adobe package predates Sigstore provenance; no security concern for a scoped, established package. ai
license uncommon-license:CC-BY-ND-4.0 AI (license): CC-BY-ND-4.0 is Adobe's intentional license choice for icon assets; not a security signal. ai

Versions (showing 6 of 6)

Version Deps Published
1.2.1 0 / 0
1.2.0 0 / 0
1.1.0 0 / 0
1.0.2 0 / 0
1.0.1 0 / 0
1.0.0 0 / 0

v1.2.1

1 finding
LOW No provenance attestation provenance

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

v1.2.0

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: garthdb → devongovett (on 2022-05-31) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2022-05-31. This could indicate a legitimate maintainer transition or an account compromise.

v1.1.0

2 findings
HIGH Publisher changed: jianliao79 → garthdb (on 2022-03-03) provenance

This version was published by a different npm account than previous versions on 2022-03-03. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v1.0.2

1 finding
INFO No provenance attestation provenance

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

v1.0.1

2 findings
HIGH Unclaimed maintainer email domain: adobeio.com email-domain

Maintainer email '[email protected]' uses domain 'adobeio.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

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

v1.0.0

2 findings
HIGH Unclaimed maintainer email domain: adobeio.com email-domain

Maintainer email '[email protected]' uses domain 'adobeio.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.