@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 100 of 137)
| Version | Deps | Published |
|---|---|---|
| 0.6.15 | 10 / 17 | |
| 0.6.14 | 10 / 17 | |
| 0.6.13 | 10 / 17 | |
| 0.6.12 | 10 / 17 | |
| 0.6.11 | 10 / 17 | |
| 0.6.10 | 10 / 17 | |
| 0.6.9 | 10 / 17 | |
| 0.6.8 | 10 / 17 | |
| 0.6.7 | 10 / 17 | |
| 0.6.6 | 10 / 17 | |
| 0.6.5 | 10 / 17 | |
| 0.6.4 | 10 / 17 | |
| 0.6.3 | 10 / 17 | |
| 0.6.2 | 10 / 17 | |
| 0.6.1 | 10 / 17 | |
| 0.6.0 | 10 / 17 | |
| 0.5.6 | 10 / 17 | |
| 0.5.5 | 10 / 17 | |
| 0.5.4 | 10 / 17 | |
| 0.5.3 | 10 / 17 | |
| 0.5.2 | 10 / 17 | |
| 0.5.1 | 10 / 17 | |
| 0.5.0 | 10 / 17 | |
| 0.4.8 | 10 / 17 | |
| 0.4.7 | 10 / 17 | |
| 0.4.6 | 10 / 17 | |
| 0.4.5 | 10 / 17 | |
| 0.4.4 | 10 / 17 | |
| 0.4.3 | 10 / 17 | |
| 0.4.2 | 10 / 17 | |
| 0.4.1 | 10 / 17 | |
| 0.4.0 | 10 / 17 | |
| 0.3.60 | 10 / 17 | |
| 0.3.59 | 10 / 17 | |
| 0.3.57 | 10 / 17 | |
| 0.3.56 | 10 / 17 | |
| 0.3.55 | 10 / 17 | |
| 0.3.54 | 10 / 17 | |
| 0.3.53 | 10 / 17 | |
| 0.3.52 | 10 / 17 | |
| 0.3.51 | 10 / 17 | |
| 0.3.50 | 10 / 17 | |
| 0.3.49 | 10 / 17 | |
| 0.3.48 | 10 / 17 | |
| 0.3.47 | 10 / 17 | |
| 0.3.46 | 10 / 17 | |
| 0.3.45 | 10 / 17 | |
| 0.3.44 | 10 / 17 | |
| 0.3.43 | 10 / 17 | |
| 0.3.42 | 10 / 17 | |
| 0.3.41 | 10 / 17 | |
| 0.3.40 | 10 / 17 | |
| 0.3.39 | 10 / 17 | |
| 0.3.38 | 10 / 17 | |
| 0.3.37 | 10 / 17 | |
| 0.3.36 | 10 / 17 | |
| 0.3.35 | 10 / 17 | |
| 0.3.34 | 10 / 17 | |
| 0.3.33 | 10 / 17 | |
| 0.3.32 | 10 / 17 | |
| 0.3.31 | 10 / 17 | |
| 0.3.30 | 10 / 17 | |
| 0.3.29 | 10 / 17 | |
| 0.3.28 | 10 / 17 | |
| 0.3.27 | 10 / 17 | |
| 0.3.26 | 10 / 17 | |
| 0.3.25 | 10 / 17 | |
| 0.3.24 | 10 / 17 | |
| 0.3.23 | 10 / 17 | |
| 0.3.22 | 10 / 17 | |
| 0.3.21 | 10 / 17 | |
| 0.3.20 | 10 / 17 | |
| 0.3.19 | 10 / 17 | |
| 0.3.18 | 10 / 17 | |
| 0.3.17 | 10 / 17 | |
| 0.3.16 | 10 / 17 | |
| 0.3.15 | 10 / 17 | |
| 0.3.14 | 10 / 17 | |
| 0.3.13 | 10 / 17 | |
| 0.3.12 | 10 / 17 | |
| 0.3.11 | 10 / 17 | |
| 0.3.10 | 10 / 17 | |
| 0.3.9 | 10 / 17 | |
| 0.3.8 | 10 / 17 | |
| 0.3.7 | 10 / 17 | |
| 0.3.6 | 10 / 17 | |
| 0.3.5 | 10 / 17 | |
| 0.3.4 | 10 / 17 | |
| 0.3.3 | 10 / 17 | |
| 0.3.2 | 10 / 17 | |
| 0.3.1 | 10 / 17 | |
| 0.3.0 | 10 / 17 | |
| 0.2.11 | 10 / 17 | |
| 0.2.10 | 10 / 17 | |
| 0.2.9 | 9 / 17 | |
| 0.2.8 | 9 / 17 | |
| 0.2.7 | 9 / 17 | |
| 0.2.6 | 9 / 17 | |
| 0.2.5 | 9 / 17 | |
| 0.2.4 | 9 / 17 |
v0.6.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.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.4.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.4.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.4.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.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.