← Home

@react-spectrum/link

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:pino AI (typosquat): Scoped Adobe React Spectrum monorepo package; Levenshtein match to 'pino' is a false positive with no plausible typosquat intent. ai
phantom-deps phantom-dep:@swc/helpers AI (phantom-deps): @swc/helpers is a known implicit runtime dependency for SWC-compiled packages; standard pattern in this monorepo. ai
phantom-deps phantom-dep:@react-types/shared AI (phantom-deps): @react-types/shared is a standard React Spectrum type dependency referenced in config files; not a phantom dep concern. ai
bogus-package bogus-package AI (bogus-package): Monorepo sub-packages routinely lack standalone README code blocks and keywords; not indicative of spam for this well-established Adobe package. ai

Versions (showing 100 of 203)

Hide prereleases
Version Deps Published
3.7.1 2 / 2
3.7.0 2 / 0
3.6.25 8 / 1
3.6.24 8 / 1
3.6.23 8 / 1
3.6.22 8 / 1
3.6.21 8 / 1
3.6.20 8 / 1
3.6.19 8 / 1
3.6.18 8 / 1
3.6.17 8 / 1
3.6.16 8 / 1
3.6.15 8 / 1
3.6.14 8 / 1
3.6.13 8 / 1
3.6.12 8 / 1
3.6.11 8 / 1
3.6.10 8 / 1
3.6.9 8 / 1
3.6.8 8 / 1
3.6.7 7 / 1
3.6.6 7 / 1
3.6.5 7 / 1
3.6.4 7 / 1
3.6.3 7 / 1
3.6.2 7 / 1
3.6.1 7 / 1
3.6.0 7 / 1
3.5.5 7 / 1
3.5.4 7 / 1
3.5.3 7 / 1
3.5.2 7 / 1
3.5.1 7 / 1
3.5.0 7 / 1
3.4.4 7 / 1
3.4.3 7 / 1
3.4.2 7 / 1
3.4.1 7 / 1
3.4.0 7 / 1
3.3.1 7 / 1
3.3.0 7 / 1
3.2.5 7 / 1
3.2.4 7 / 1
3.2.3 7 / 1
3.2.2 7 / 1
3.2.1 7 / 1
3.2.0 7 / 1
3.1.3 7 / 1
3.1.2 7 / 1
3.1.1 7 / 1
3.1.0 7 / 1
3.0.2 5 / 1
3.0.1 5 / 1
3.0.0 5 / 1
3.0.0-nightly-ffb1a9d0d-260323 2 / 0
3.0.0-nightly-ff8f6f319-251118 8 / 1
3.0.0-nightly-fc3ea3e8c-251029 8 / 1
3.0.0-nightly-f8d513f06-251119 8 / 1
3.0.0-nightly-f61e75cea-251124 8 / 1
3.0.0-nightly-f61e75cea-251123 8 / 1
3.0.0-nightly-f3e3157d0-260219 8 / 1
3.0.0-nightly-f3e3157d0-260218 8 / 1
3.0.0-nightly-f1aafc6ce-251105 8 / 1
3.0.0-nightly-efc581c91-260413 2 / 0
3.0.0-nightly-eef731921-260216 8 / 1
3.0.0-nightly-eef731921-260215 8 / 1
3.0.0-nightly-eef731921-260214 8 / 1
3.0.0-nightly-eec6c1a4d-251223 8 / 1
3.0.0-nightly-ee49fdbaf-260306 8 / 1
3.0.0-nightly-ec7736d18-260421 2 / 0
3.0.0-nightly-e3913baaa-260422 2 / 0
3.0.0-nightly-e24140214-260309 8 / 1
3.0.0-nightly-e24140214-260308 8 / 1
3.0.0-nightly-e24140214-260307 8 / 1
3.0.0-nightly-daafdd59d-260224 8 / 1
3.0.0-nightly-daafdd59d-260223 8 / 1
3.0.0-nightly-daafdd59d-260222 8 / 1
3.0.0-nightly-daafdd59d-260221 8 / 1
3.0.0-nightly-d974b93de-260227 8 / 1
3.0.0-nightly-cfb620016-260126 8 / 1
3.0.0-nightly-cfb620016-260125 8 / 1
3.0.0-nightly-cfb620016-260124 8 / 1
3.0.0-nightly-cf7c1541e-251113 8 / 1
3.0.0-nightly-cdbfe4816-260303 8 / 1
3.0.0-nightly-c8d64314e-260208 8 / 1
3.0.0-nightly-c8d64314e-260207 8 / 1
3.0.0-nightly-c80e3d1d6-251212 8 / 1
3.0.0-nightly-c5a3ae829-260331 2 / 0
3.0.0-nightly-c2517d3bb-260115 8 / 1
3.0.0-nightly-beda77877-260414 2 / 0
3.0.0-nightly-b557ca906-251216 8 / 1
3.0.0-nightly-b4382b073-260130 8 / 1
3.0.0-nightly-b321d7de8-260122 8 / 1
3.0.0-nightly-b321d7de8-260121 8 / 1
3.0.0-nightly-ac718c6cd-260402 2 / 0
3.0.0-nightly-ab5e6f3db-251110 8 / 1
3.0.0-nightly-ab5e6f3db-251109 8 / 1
3.0.0-nightly-ab5e6f3db-251108 8 / 1
3.0.0-nightly-ab5e6f3db-251107 8 / 1
3.0.0-nightly-a9fccbde0-260302 8 / 1
Showing 100 of 203 Next page →

v3.7.1

1 finding
LOW No provenance attestation provenance

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

v3.7.0

1 finding
LOW No provenance attestation provenance

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

v3.6.25

1 finding
LOW No provenance attestation provenance

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

v3.6.24

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

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

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

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

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

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

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

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

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

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

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

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

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

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.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.6.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.6.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.6.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.6.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.6.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.6.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.6.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.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.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.5.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.5.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.5.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.5.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.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.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.4.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.4.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.4.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.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.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.2.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.2.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.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.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.1.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.1.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.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.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.0.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.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.