@emeryld/ui
A React UI components package with provider-first theming.
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped UI library; name similarity to uuid is coincidental, not impersonation. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped UI library; name similarity to pg is coincidental, not impersonation. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped UI library; name similarity to qs is coincidental, not impersonation. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped UI library; name similarity to joi is coincidental, not impersonation. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped UI library; name similarity to yup is coincidental, not impersonation. | ai | |
| phantom-deps | phantom-dep:postcss | AI (phantom-deps): postcss is a declared runtime dependency used in build config; phantom-dep heuristic misfires here. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.2.7 | 1 / 15 | |
| 0.2.6 | 1 / 15 | |
| 0.2.5 | 1 / 15 | |
| 0.2.4 | 1 / 15 | |
| 0.2.3 | 1 / 15 | |
| 0.2.2 | 1 / 15 | |
| 0.2.1 | 1 / 15 | |
| 0.2.0 | 1 / 15 | |
| 0.1.7 | 1 / 15 | |
| 0.1.6 | 1 / 15 | |
| 0.1.5 | 1 / 15 | |
| 0.1.4 | 1 / 15 | |
| 0.1.3 | 1 / 15 | |
| 0.1.2 | 1 / 15 | |
| 0.1.1 | 1 / 15 | |
| 0.1.0 | 1 / 15 |
v0.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
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.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.