← Home

@react-types/view

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:vite AI (typosquat): @react-types/view is an official Adobe React Spectrum type package, not a typosquat of vite. The name similarity is purely coincidental; this package predates vite's popularity and is part of a well-known monorepo. ai
bogus-package bogus-package AI (bogus-package): Type-definition-only packages in the @react-types/* family legitimately have minimal READMEs and no keywords; this is consistent across the entire React Spectrum monorepo. ai

Versions (showing 100 of 189)

Hide prereleases
Version Deps Published
3.5.0 1 / 0
3.4.23 1 / 0
3.4.22 1 / 0
3.4.21 1 / 0
3.4.20 1 / 0
3.4.19 1 / 0
3.4.18 1 / 0
3.4.17 1 / 0
3.4.16 1 / 0
3.4.15 1 / 0
3.4.14 1 / 0
3.4.13 1 / 0
3.4.12 1 / 0
3.4.11 1 / 0
3.4.10 1 / 0
3.4.9 1 / 0
3.4.8 1 / 0
3.4.7 1 / 0
3.4.6 1 / 0
3.4.5 1 / 0
3.4.4 1 / 0
3.4.3 1 / 0
3.4.2 1 / 0
3.4.1 1 / 0
3.4.0 1 / 0
3.3.0 1 / 0
3.2.4 1 / 0
3.2.3 1 / 0
3.2.2 1 / 0
3.2.1 1 / 0
3.2.0 1 / 0
3.1.6 1 / 0
3.1.5 1 / 0
3.1.4 1 / 0
3.1.3 1 / 0
3.1.2 1 / 0
3.1.1 1 / 0
3.1.0 1 / 0
3.0.2 1 / 0
3.0.1 1 / 0
3.0.0 1 / 0
3.0.0-nightly-ffb1a9d0d-260323 1 / 0
3.0.0-nightly-ff8f6f319-251118 1 / 0
3.0.0-nightly-fc3ea3e8c-251029 1 / 0
3.0.0-nightly-f8d513f06-251119 1 / 0
3.0.0-nightly-f61e75cea-251124 1 / 0
3.0.0-nightly-f61e75cea-251123 1 / 0
3.0.0-nightly-f3e3157d0-260219 1 / 0
3.0.0-nightly-f3e3157d0-260218 1 / 0
3.0.0-nightly-f1aafc6ce-251105 1 / 0
3.0.0-nightly-efc581c91-260413 1 / 0
3.0.0-nightly-eef731921-260216 1 / 0
3.0.0-nightly-eef731921-260215 1 / 0
3.0.0-nightly-eef731921-260214 1 / 0
3.0.0-nightly-eec6c1a4d-251223 1 / 0
3.0.0-nightly-ee49fdbaf-260306 1 / 0
3.0.0-nightly-ec7736d18-260421 1 / 0
3.0.0-nightly-e3913baaa-260422 1 / 0
3.0.0-nightly-e24140214-260309 1 / 0
3.0.0-nightly-e24140214-260308 1 / 0
3.0.0-nightly-e24140214-260307 1 / 0
3.0.0-nightly-daafdd59d-260224 1 / 0
3.0.0-nightly-daafdd59d-260223 1 / 0
3.0.0-nightly-daafdd59d-260222 1 / 0
3.0.0-nightly-daafdd59d-260221 1 / 0
3.0.0-nightly-d974b93de-260227 1 / 0
3.0.0-nightly-cfb620016-260126 1 / 0
3.0.0-nightly-cfb620016-260125 1 / 0
3.0.0-nightly-cfb620016-260124 1 / 0
3.0.0-nightly-cf7c1541e-251113 1 / 0
3.0.0-nightly-cdbfe4816-260303 1 / 0
3.0.0-nightly-c8d64314e-260208 1 / 0
3.0.0-nightly-c8d64314e-260207 1 / 0
3.0.0-nightly-c80e3d1d6-251212 1 / 0
3.0.0-nightly-c5a3ae829-260331 1 / 0
3.0.0-nightly-c2517d3bb-260115 1 / 0
3.0.0-nightly-beda77877-260414 1 / 0
3.0.0-nightly-b4382b073-260130 1 / 0
3.0.0-nightly-b321d7de8-260122 1 / 0
3.0.0-nightly-b321d7de8-260121 1 / 0
3.0.0-nightly-ac718c6cd-260402 1 / 0
3.0.0-nightly-ab5e6f3db-251110 1 / 0
3.0.0-nightly-ab5e6f3db-251109 1 / 0
3.0.0-nightly-ab5e6f3db-251108 1 / 0
3.0.0-nightly-ab5e6f3db-251107 1 / 0
3.0.0-nightly-a9fccbde0-260302 1 / 0
3.0.0-nightly-a9fccbde0-260301 1 / 0
3.0.0-nightly-a9fccbde0-260228 1 / 0
3.0.0-nightly-a911b98f1-260325 1 / 0
3.0.0-nightly-a911b98f1-260324 1 / 0
3.0.0-nightly-a90e8f141-251218 1 / 0
3.0.0-nightly-a6e720d35-260304 1 / 0
3.0.0-nightly-9e18b4a28-260412 1 / 0
3.0.0-nightly-9e18b4a28-260411 1 / 0
3.0.0-nightly-9da8c73d9-251027 1 / 0
3.0.0-nightly-9da8c73d9-251026 1 / 0
3.0.0-nightly-9da8c73d9-251025 1 / 0
3.0.0-nightly-973473718-260305 1 / 0
3.0.0-nightly-953488a1a-260108 1 / 0
3.0.0-nightly-93d39fd65-251117 1 / 0
Showing 100 of 189 Next page →

v3.5.0

1 finding
LOW No provenance attestation provenance

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

v3.4.23

1 finding
LOW No provenance attestation provenance

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

v3.4.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.4.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.4.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.4.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.4.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.4.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.4.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.4.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.4.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.4.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.4.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.4.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.4.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.4.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.4.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.4.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.4.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.4.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.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.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.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.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.1.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.1.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.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.