@shoppexio/ui
Shoppex UI components for building storefronts
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-slot | AI (phantom-deps): Radix UI deps are declared in dependencies and used in UI components; heuristic false positive for component libraries. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-dialog | AI (phantom-deps): Same as above; component library usage pattern. | ai | |
| phantom-deps | phantom-dep:class-variance-authority | AI (phantom-deps): CVA is a standard styling utility for component libraries; heuristic false positive. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped @shoppexio/ui is not a plausible typosquat of unscoped 'uuid'. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @shoppexio/ui is not a plausible typosquat of unscoped 'pg'. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @shoppexio/ui is not a plausible typosquat of unscoped 'qs'. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @shoppexio/ui is not a plausible typosquat of unscoped 'joi'. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped @shoppexio/ui is not a plausible typosquat of unscoped 'yup'. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.1.15 | 9 / 14 | |
| 0.1.12 | 9 / 13 | |
| 0.1.11 | 9 / 13 | |
| 0.1.10 | 9 / 13 | |
| 0.1.4 | 9 / 9 | |
| 0.1.3 | 9 / 9 | |
| 0.1.2 | 9 / 9 | |
| 0.1.0 | 9 / 9 |
v0.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.