@geenius/ui
Geenius UI — Shared component library for React and Solid, including HeroUI-backed React variants
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:packages/react-native/dist/index-CRRGsJ98.d.ts | AI (source-diff): TypeScript .d.ts with long interface lines, not obfuscated code. | ai | |
| phantom-deps | phantom-dep:@geenius/config | AI (phantom-deps): Same-org config dep; likely consumed transitively or via tooling. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped UI library; name similarity to qs is coincidental. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped UI library; name similarity to uuid is coincidental, not impersonation. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped UI library; name similarity to yup is coincidental. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped UI library; name similarity to joi is coincidental. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped UI library; name similarity to pg is coincidental. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 0.19.0 | 3 / 37 | |
| 0.18.0 | 0 / 30 | |
| 0.17.0 | 0 / 18 | |
| 0.16.0 | 0 / 18 |
v0.19.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mxn2020.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.