@uiid/forms
Form components — Input, Select, Checkbox, Radio, Switch, and more
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped UI design-system package; Levenshtein match to 'cors' is purely coincidental with no semantic overlap. | ai | |
| phantom-deps | phantom-dep:@uiid/tokens | AI (phantom-deps): Same-org monorepo sibling; may be used transitively or in CSS/config rather than direct JS imports. | ai | |
| phantom-deps | phantom-dep:@uiid/buttons | AI (phantom-deps): Same-org monorepo sibling; phantom detection likely misses indirect usage patterns in design systems. | ai | |
| phantom-deps | phantom-dep:@number-flow/react | AI (phantom-deps): Noted as referenced in config files; stable false positive for this package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.0.22 | 11 / 23 | |
| 0.0.21 | 11 / 23 | |
| 0.0.20 | 11 / 23 | |
| 0.0.19 | 11 / 23 | |
| 0.0.18 | 11 / 25 | |
| 0.0.17 | 11 / 25 | |
| 0.0.16 | 11 / 25 | |
| 0.0.15 | 11 / 25 | |
| 0.0.14 | 11 / 25 | |
| 0.0.12 | 11 / 25 | |
| 0.0.11 | 11 / 25 | |
| 0.0.10 | 11 / 25 | |
| 0.0.8 | 11 / 25 | |
| 0.0.7 | 11 / 25 |
v0.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.