@synerity/ui
Synerity UI — styled component library with zero-runtime CSS
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:uuid | AI (typosquat): Scoped UI library; no plausible impersonation of uuid. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped UI library; no plausible impersonation of pg. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped UI library; no plausible impersonation of qs. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped UI library; no plausible impersonation of joi. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped UI library; no plausible impersonation of yup. | ai | |
| phantom-deps | phantom-dep:@synerity/tokens | AI (phantom-deps): Same-org sibling dep; likely consumed via CSS/build pipeline rather than direct JS import. | ai |
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.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.