← Home

@react-spectrum/list

npm Repository Homepage

Spectrum UI components in React

100
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

devongovettaspro83

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:jest AI (typosquat): @react-spectrum/list is an official Adobe React Spectrum component, not a typosquat of jest. The scoped namespace clearly identifies it as part of Adobe's design system. ai
phantom-deps phantom-dep:@swc/helpers AI (phantom-deps): @swc/helpers is a known implicit runtime dependency for SWC-compiled packages; its presence as a declared dep is the correct pattern for this build toolchain. ai

Versions (showing 100 of 192)

Hide prereleases
Version Deps Published
3.11.1 3 / 2
3.11.0 3 / 0
3.10.11 24 / 4
3.10.10 24 / 4
3.10.9 24 / 4
3.10.8 24 / 4
3.10.7 24 / 4
3.10.6 24 / 4
3.10.5 24 / 4
3.10.4 24 / 4
3.10.3 24 / 4
3.10.2 24 / 4
3.10.1 24 / 4
3.10.0 24 / 4
3.9.3 24 / 4
3.9.2 24 / 4
3.9.1 24 / 4
3.9.0 24 / 4
3.8.3 24 / 4
3.8.2 24 / 4
3.8.1 24 / 4
3.8.0 24 / 4
3.7.10 22 / 4
3.7.9 22 / 4
3.7.8 22 / 4
3.7.7 22 / 4
3.7.6 22 / 4
3.7.5 22 / 4
3.7.4 22 / 4
3.7.3 22 / 4
3.7.2 22 / 4
3.7.1 23 / 4
3.7.0 23 / 4
3.6.2 23 / 4
3.6.1 23 / 4
3.6.0 23 / 4
3.5.0 23 / 4
3.4.0 23 / 4
3.3.1 23 / 4
3.3.0 23 / 4
3.2.2 23 / 4
3.2.1 23 / 4
3.2.0 22 / 5
3.1.0 22 / 5
3.0.0 24 / 4
3.0.0-nightly-ffb1a9d0d-260323 3 / 0
3.0.0-nightly-ff8f6f319-251118 24 / 4
3.0.0-nightly-fc3ea3e8c-251029 24 / 4
3.0.0-nightly-f8d513f06-251119 24 / 4
3.0.0-nightly-f61e75cea-251124 24 / 4
3.0.0-nightly-f61e75cea-251123 24 / 4
3.0.0-nightly-f3e3157d0-260219 24 / 4
3.0.0-nightly-f3e3157d0-260218 24 / 4
3.0.0-nightly-f1aafc6ce-251105 24 / 4
3.0.0-nightly-efc581c91-260413 3 / 0
3.0.0-nightly-eef731921-260216 24 / 4
3.0.0-nightly-eef731921-260215 24 / 4
3.0.0-nightly-eef731921-260214 24 / 4
3.0.0-nightly-eec6c1a4d-251223 24 / 4
3.0.0-nightly-ee49fdbaf-260306 24 / 4
3.0.0-nightly-ec7736d18-260421 3 / 0
3.0.0-nightly-e3913baaa-260422 3 / 0
3.0.0-nightly-e24140214-260309 24 / 4
3.0.0-nightly-e24140214-260308 24 / 4
3.0.0-nightly-e24140214-260307 24 / 4
3.0.0-nightly-daafdd59d-260224 24 / 4
3.0.0-nightly-daafdd59d-260223 24 / 4
3.0.0-nightly-daafdd59d-260222 24 / 4
3.0.0-nightly-daafdd59d-260221 24 / 4
3.0.0-nightly-d974b93de-260227 24 / 4
3.0.0-nightly-cfb620016-260126 24 / 4
3.0.0-nightly-cfb620016-260125 24 / 4
3.0.0-nightly-cfb620016-260124 24 / 4
3.0.0-nightly-cf7c1541e-251113 24 / 4
3.0.0-nightly-cdbfe4816-260303 24 / 4
3.0.0-nightly-c8d64314e-260208 24 / 4
3.0.0-nightly-c8d64314e-260207 24 / 4
3.0.0-nightly-c80e3d1d6-251212 24 / 4
3.0.0-nightly-c5a3ae829-260331 3 / 0
3.0.0-nightly-c2517d3bb-260115 24 / 4
3.0.0-nightly-beda77877-260414 3 / 0
3.0.0-nightly-b4382b073-260130 24 / 4
3.0.0-nightly-b321d7de8-260122 24 / 4
3.0.0-nightly-b321d7de8-260121 24 / 4
3.0.0-nightly-ac718c6cd-260402 3 / 0
3.0.0-nightly-ab5e6f3db-251110 24 / 4
3.0.0-nightly-ab5e6f3db-251109 24 / 4
3.0.0-nightly-ab5e6f3db-251108 24 / 4
3.0.0-nightly-ab5e6f3db-251107 24 / 4
3.0.0-nightly-a9fccbde0-260302 24 / 4
3.0.0-nightly-a9fccbde0-260301 24 / 4
3.0.0-nightly-a9fccbde0-260228 24 / 4
3.0.0-nightly-a911b98f1-260325 3 / 0
3.0.0-nightly-a911b98f1-260324 3 / 0
3.0.0-nightly-a90e8f141-251218 24 / 4
3.0.0-nightly-a6e720d35-260304 24 / 4
3.0.0-nightly-9e18b4a28-260412 3 / 0
3.0.0-nightly-9e18b4a28-260411 3 / 0
3.0.0-nightly-9da8c73d9-251027 24 / 4
3.0.0-nightly-9da8c73d9-251026 24 / 4
Showing 100 of 192 Next page →

v3.11.1

1 finding
LOW No provenance attestation provenance

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

v3.11.0

1 finding
LOW No provenance attestation provenance

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

v3.10.11

1 finding
LOW No provenance attestation provenance

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

v3.10.10

1 finding
LOW No provenance attestation provenance

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

v3.10.9

1 finding
LOW No provenance attestation provenance

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

v3.10.8

1 finding
LOW No provenance attestation provenance

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

v3.10.7

1 finding
LOW No provenance attestation provenance

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

v3.10.6

1 finding
LOW No provenance attestation provenance

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

v3.10.5

1 finding
LOW No provenance attestation provenance

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

v3.10.4

1 finding
LOW No provenance attestation provenance

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

v3.10.3

1 finding
LOW No provenance attestation provenance

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

v3.10.2

1 finding
LOW No provenance attestation provenance

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

v3.10.1

1 finding
LOW No provenance attestation provenance

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

v3.10.0

1 finding
LOW No provenance attestation provenance

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

v3.9.3

1 finding
LOW No provenance attestation provenance

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

v3.9.2

1 finding
LOW No provenance attestation provenance

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

v3.9.1

1 finding
LOW No provenance attestation provenance

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

v3.9.0

1 finding
LOW No provenance attestation provenance

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

v3.8.3

1 finding
LOW No provenance attestation provenance

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

v3.8.2

1 finding
LOW No provenance attestation provenance

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

v3.8.1

1 finding
LOW No provenance attestation provenance

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

v3.8.0

1 finding
LOW No provenance attestation provenance

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

v3.7.10

1 finding
LOW No provenance attestation provenance

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

v3.7.9

1 finding
LOW No provenance attestation provenance

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

v3.7.8

1 finding
LOW No provenance attestation provenance

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

v3.7.7

1 finding
LOW No provenance attestation provenance

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

v3.7.6

1 finding
LOW No provenance attestation provenance

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

v3.7.5

1 finding
LOW No provenance attestation provenance

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

v3.7.4

1 finding
LOW No provenance attestation provenance

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

v3.7.3

1 finding
LOW No provenance attestation provenance

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

v3.7.2

1 finding
LOW No provenance attestation provenance

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

v3.7.1

1 finding
LOW No provenance attestation provenance

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

v3.7.0

1 finding
LOW No provenance attestation provenance

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

v3.6.2

1 finding
LOW No provenance attestation provenance

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

v3.6.1

1 finding
LOW No provenance attestation provenance

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

v3.6.0

1 finding
LOW No provenance attestation provenance

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

v3.5.0

1 finding
LOW No provenance attestation provenance

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

v3.4.0

1 finding
LOW No provenance attestation provenance

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

v3.3.1

1 finding
LOW No provenance attestation provenance

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

v3.3.0

1 finding
LOW No provenance attestation provenance

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

v3.2.2

1 finding
LOW No provenance attestation provenance

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

v3.2.1

1 finding
LOW No provenance attestation provenance

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

v3.2.0

1 finding
LOW No provenance attestation provenance

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

v3.1.0

1 finding
LOW No provenance attestation provenance

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

v3.0.0

1 finding
LOW No provenance attestation provenance

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