@uniai-fe/uds-primitives
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@radix-ui/react-toggle-group | AI (phantom-deps): Same as @radix-ui/react-slot — component library pattern. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-slot | AI (phantom-deps): Radix UI deps used via config/re-exports in component library; stable false positive. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-primitive | AI (phantom-deps): Same as @radix-ui/react-slot — component library pattern. | ai | |
| phantom-deps | phantom-dep:@mantine/core | AI (phantom-deps): Mantine deps are declared runtime dependencies used via config/re-exports in a component library; stable false positive. | ai | |
| phantom-deps | phantom-dep:@mantine/dates | AI (phantom-deps): Same as @mantine/core — component library config pattern. | ai | |
| phantom-deps | phantom-dep:@mantine/hooks | AI (phantom-deps): Same as @mantine/core — component library config pattern. | ai | |
| dependencies | unvetted-dep:react-daum-postcode | AI (dependencies): react-daum-postcode is a well-known Korean address search library; stable legitimate dependency for this package. | ai | |
| provenance | no-provenance | AI (provenance): Internal design system package; provenance absence is common and not a risk signal here. | ai |
Versions (showing 38 of 141)
| Version | Deps | Published |
|---|---|---|
| 0.2.3 | 9 / 17 | |
| 0.2.2 | 9 / 15 | |
| 0.2.1 | 8 / 15 | |
| 0.2.0 | 8 / 15 | |
| 0.1.13 | 11 / 15 | |
| 0.1.12 | 11 / 15 | |
| 0.1.11 | 11 / 15 | |
| 0.1.10 | 11 / 15 | |
| 0.1.8 | 11 / 15 | |
| 0.1.7 | 11 / 15 | |
| 0.1.6 | 11 / 15 | |
| 0.1.5 | 11 / 15 | |
| 0.1.4 | 11 / 15 | |
| 0.1.3 | 11 / 15 | |
| 0.1.2 | 11 / 15 | |
| 0.1.1 | 11 / 15 | |
| 0.1.0 | 11 / 15 | |
| 0.0.21 | 11 / 15 | |
| 0.0.20 | 11 / 15 | |
| 0.0.19 | 12 / 17 | |
| 0.0.18 | 12 / 17 | |
| 0.0.17 | 12 / 17 | |
| 0.0.16 | 12 / 17 | |
| 0.0.15 | 12 / 17 | |
| 0.0.14 | 12 / 17 | |
| 0.0.13 | 12 / 17 | |
| 0.0.12 | 12 / 17 | |
| 0.0.11 | 12 / 17 | |
| 0.0.10 | 12 / 17 | |
| 0.0.9 | 12 / 17 | |
| 0.0.8 | 12 / 17 | |
| 0.0.7 | 12 / 17 | |
| 0.0.6 | 12 / 16 | |
| 0.0.5 | 12 / 16 | |
| 0.0.4 | 12 / 16 | |
| 0.0.3 | 12 / 16 | |
| 0.0.2 | 13 / 15 | |
| 0.0.1 | 13 / 15 |
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.