@codefast/ui
Core UI components library built with React and Tailwind 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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@radix-ui/react-direction | AI (phantom-deps): Radix direction is a transitive peer used via config; not directly imported but legitimately referenced. | ai | |
| dependencies | unvetted-dep:@radix-ui/react-avatar | AI (dependencies): @radix-ui/react-avatar is a well-known, widely-used primitive; stable false positive for this UI library. | ai | |
| dependencies | unvetted-dep:@radix-ui/react-hover-card | AI (dependencies): @radix-ui/react-hover-card is a well-known, widely-used primitive; stable false positive for this UI library. | ai | |
| phantom-deps | phantom-dep:date-fns | AI (phantom-deps): date-fns is a legitimate runtime dep used by the calendar component via react-day-picker; phantom-dep is a false positive here. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped UI component library; not a typosquat of yup. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped UI component library; not a typosquat of uuid. | ai | |
| phantom-deps | phantom-dep:tw-animate-css | AI (phantom-deps): tw-animate-css is a CSS-only dep referenced in config files, not JS imports; phantom-dep false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped UI component library; not a typosquat of pg. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped UI component library; not a typosquat of qs. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped UI component library; not a typosquat of joi. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.3.15 | 46 / 17 | |
| 0.3.14 | 46 / 17 | |
| 0.3.13 | 46 / 17 | |
| 0.3.12 | 47 / 19 | |
| 0.3.10 | 47 / 22 | |
| 0.3.9 | 47 / 22 | |
| 0.3.8 | 47 / 22 | |
| 0.3.1 | 48 / 22 |
v0.3.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.