@medusajs/ui
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:cva | AI (dependencies): cva (class-variance-authority) is a well-known UI utility; beta pin is intentional for this package. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): @medusajs/ui is a legitimate scoped package, not a typosquat of pg. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): @medusajs/ui is a legitimate scoped package, not a typosquat of qs. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @medusajs/ui is a legitimate scoped package, not a typosquat of joi. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): @medusajs/ui is a legitimate scoped package, not a typosquat of uuid. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-dialog | AI (phantom-deps): Declared as runtime dep and used via re-exports; phantom-dep heuristic fires on config-only references. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-dismissable-layer | AI (phantom-deps): Same as above; legitimate runtime dependency referenced in config. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): @medusajs/ui is a legitimate scoped package, not a typosquat of yup. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 4.1.13 | 19 / 3 | |
| 4.1.12 | 19 / 3 | |
| 4.1.11 | 19 / 3 | |
| 4.1.10 | 19 / 3 | |
| 4.1.9 | 19 / 3 | |
| 4.1.6 | 19 / 3 | |
| 4.1.1 | 18 / 3 | |
| 4.0.30 | 18 / 3 |
v4.1.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.