@react-types/text Apache-2.0 42 versions

@react-types/text

npm Repository Homepage

Spectrum UI components in React

42

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.

Source	Rule	Reason	Accepted by	When
typosquat	typosquat.levenshtein:next	AI (typosquat): @react-types/text is a legitimate Adobe React Spectrum type package; no meaningful similarity to 'next' — scoped namespace and purpose are entirely different.	ai	2026/04/23
typosquat	typosquat.levenshtein:nuxt	AI (typosquat): @react-types/text is a legitimate Adobe React Spectrum type package; no meaningful similarity to 'nuxt' — scoped namespace and purpose are entirely different.	ai	2026/04/23
typosquat	typosquat.levenshtein:jest	AI (typosquat): @react-types/text is a legitimate Adobe React Spectrum type package; no meaningful similarity to 'jest' — scoped namespace and purpose are entirely different.	ai	2026/04/23
bogus-package	bogus-package	AI (bogus-package): Type-definition packages in a monorepo commonly lack keywords and verbose READMEs; this is a well-established Adobe React Spectrum package with 1293 versions.	ai	2026/04/23

Versions (showing 42 of 42)

Show 148 prereleases

Version	Deps	Published
3.4.0	1 / 0	2026-04-14
3.3.23	1 / 0	2026-03-04
3.3.22	1 / 0	2026-02-04
3.3.21	1 / 0	2025-10-02
3.3.20	1 / 0	2025-08-25
3.3.19	1 / 0	2025-07-23
3.3.18	1 / 0	2025-06-05
3.3.17	1 / 0	2025-05-19
3.3.16	1 / 0	2025-04-11
3.3.15	1 / 0	2025-03-06
3.3.14	1 / 0	2025-01-15
3.3.13	1 / 0	2024-11-21
3.3.12	1 / 0	2024-10-01
3.3.11	1 / 0	2024-07-24
3.3.10	1 / 0	2024-07-22
3.3.9	1 / 0	2024-05-20
3.3.8	1 / 0	2024-05-02
3.3.7	1 / 0	2024-02-15
3.3.6	1 / 0	2023-11-09
3.3.5	1 / 0	2023-10-02
3.3.4	1 / 0	2023-09-07
3.3.3	1 / 0	2023-08-09
3.3.2	1 / 0	2023-05-24
3.3.1	1 / 0	2023-04-05
3.3.0	1 / 0	2023-02-23
3.2.5	1 / 0	2022-11-16
3.2.4	1 / 0	2022-10-04
3.2.3	1 / 0	2022-08-26
3.2.2	1 / 0	2022-07-28
3.2.1	1 / 0	2022-06-15
3.2.0	1 / 0	2022-05-31
3.1.7	1 / 0	2022-05-03
3.1.6	1 / 0	2022-03-07
3.1.5	1 / 0	2022-02-16
3.1.4	1 / 0	2022-02-15
3.1.3	1 / 0	2021-08-04
3.1.2	1 / 0	2021-02-17
3.1.1	1 / 0	2020-10-01
3.1.0	1 / 0	2020-07-23
3.0.2	1 / 0	2020-07-15
3.0.1	1 / 0	2020-07-13
3.0.0	1 / 0	2020-06-24

v3.4.0

1 finding

LOW No provenance attestation provenance

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

v3.3.23

1 finding

LOW No provenance attestation provenance

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

v3.3.22

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'next' typosquat

Package name '@react-types/text' is 1 edit(s) away from popular package 'next'.

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