@mieweb/ui
A themeable, accessible React component library built with 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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): @mieweb/ui is a scoped React UI library by Medical Informatics Engineering; Levenshtein match to 'uuid' is a false positive with no impersonation intent. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): @mieweb/ui is a scoped React UI library; Levenshtein match to 'pg' is a false positive with no impersonation intent. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): @mieweb/ui is a scoped React UI library; Levenshtein match to 'qs' is a false positive with no impersonation intent. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @mieweb/ui is a scoped React UI library; Levenshtein match to 'joi' is a false positive with no impersonation intent. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): @mieweb/ui is a scoped React UI library; Levenshtein match to 'yup' is a false positive with no impersonation intent. | ai | |
| phantom-deps | phantom-dep:@swc/helpers | AI (phantom-deps): @swc/helpers is a known implicit runtime dependency for SWC-compiled bundles; declared as a direct dep and used implicitly by compiled output. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.2.4 | 6 / 40 | |
| 0.2.2 | 6 / 40 | |
| 0.2.1 | 5 / 38 | |
| 0.2.0 | 5 / 38 | |
| 0.1.1 | 5 / 38 | |
| 0.1.0 | 5 / 38 |
v0.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
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.