@radix-ui/react-form
View docs [here](https://radix-ui.com/primitives/docs/components/form).
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legitimate transition to GitHub Actions CI/CD publishing with SLSA provenance for radix-ui org. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): npm-workos reflects WorkOS ownership of Radix UI; legitimate org transition. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Old individual maintainers replaced by org account; expected during org transition. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Radix UI primitives packages historically have minimal descriptions. | ai | |
| typosquat | typosquat.levenshtein:react-dom | AI (typosquat): @radix-ui/react-form is a legitimate scoped package in the official Radix UI primitives library; the Levenshtein match to react-dom is purely coincidental and not a typosquat. | ai | |
| bogus-package | bogus-package | AI (bogus-package): This is a well-known UI component library; sparse README/keywords are a style choice, not a spam indicator. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.1.9 | 6 / 7 | |
| 0.1.8 | 6 / 9 | |
| 0.1.7 | 6 / 9 | |
| 0.1.6 | 6 / 9 | |
| 0.1.5 | 6 / 9 |
v0.1.9
2 findingsThis version was published by a different npm account than previous versions on 2026-06-06. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.