@mesob/ui
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@radix-ui/react-avatar | AI (dependencies): Standard Radix UI primitive; widely used in the ecosystem. | ai | |
| dependencies | unvetted-dep:@radix-ui/react-hover-card | AI (dependencies): Standard Radix UI primitive; widely used in the ecosystem. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Active UI library with 48 versions and real download traffic; missing metadata is sloppy but not malicious. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): zod is a peer/config-level dependency in a UI library; phantom-dep false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped UI library; no resemblance to yup — Levenshtein false positive. | ai | |
| phantom-deps | phantom-dep:ahooks | AI (phantom-deps): Re-exported or used indirectly; stable false positive for this UI library. | ai | |
| phantom-deps | phantom-dep:date-fns | AI (phantom-deps): Re-exported or used indirectly; stable false positive for this UI library. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped UI library; no resemblance to uuid — Levenshtein false positive. | ai | |
| phantom-deps | phantom-dep:tw-animate-css | AI (phantom-deps): CSS utility; not directly imported in JS — stable false positive. | ai | |
| phantom-deps | phantom-dep:@hookform/resolvers | AI (phantom-deps): Re-exported or used indirectly; stable false positive for this UI library. | ai | |
| phantom-deps | phantom-dep:react-use | AI (phantom-deps): Re-exported or used indirectly; stable false positive for this UI library. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped UI library; no resemblance to pg — Levenshtein false positive. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped UI library; no resemblance to qs — Levenshtein false positive. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped UI library; no resemblance to joi — Levenshtein false positive. | ai |
Versions (showing 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 0.6.17 | 45 / 8 | |
| 0.6.16 | 45 / 8 | |
| 0.6.15 | 45 / 8 | |
| 0.6.14 | 45 / 8 | |
| 0.6.13 | 45 / 8 | |
| 0.6.12 | 45 / 8 | |
| 0.6.11 | 46 / 10 | |
| 0.6.10 | 46 / 10 | |
| 0.6.9 | 45 / 10 | |
| 0.6.8 | 45 / 10 | |
| 0.6.7 | 45 / 10 | |
| 0.6.6 | 45 / 10 | |
| 0.6.5 | 45 / 10 | |
| 0.6.4 | 45 / 10 | |
| 0.6.3 | 45 / 10 | |
| 0.6.2 | 45 / 10 | |
| 0.6.1 | 46 / 8 | |
| 0.6.0 | 45 / 8 | |
| 0.5.11 | 43 / 8 | |
| 0.5.10 | 43 / 8 | |
| 0.5.9 | 43 / 8 | |
| 0.5.8 | 43 / 8 | |
| 0.5.7 | 43 / 8 | |
| 0.5.6 | 43 / 8 | |
| 0.5.5 | 43 / 8 | |
| 0.5.4 | 43 / 8 | |
| 0.5.3 | 43 / 8 | |
| 0.5.2 | 43 / 8 | |
| 0.5.0 | 43 / 8 | |
| 0.4.7 | 43 / 8 | |
| 0.4.6 | 43 / 8 | |
| 0.4.5 | 43 / 8 | |
| 0.4.4 | 42 / 8 | |
| 0.4.3 | 42 / 8 | |
| 0.4.2 | 42 / 8 | |
| 0.4.1 | 42 / 8 | |
| 0.4.0 | 42 / 8 | |
| 0.3.5 | 42 / 8 | |
| 0.3.4 | 41 / 8 | |
| 0.3.3 | 41 / 8 | |
| 0.3.2 | 41 / 8 | |
| 0.3.1 | 41 / 8 | |
| 0.3.0 | 41 / 8 | |
| 0.0.7 | 47 / 10 |
v0.6.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
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.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.