@pelatform/ui
A Modern and Minimal React UI Library built with TailwindCSS.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@base-ui-components/react | AI (dependencies): @base-ui-components/react is a legitimate MUI headless UI library; beta version pin is expected for this package. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped org package @pelatform/ui; not a typosquat of pg — coincidental Levenshtein match. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped org package @pelatform/ui; not a typosquat of qs — coincidental Levenshtein match. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped org package @pelatform/ui; not a typosquat of uuid — coincidental Levenshtein match. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped org package @pelatform/ui; not a typosquat of yup — coincidental Levenshtein match. | ai | |
| phantom-deps | phantom-dep:tw-animate-css | AI (phantom-deps): tw-animate-css is a declared runtime dependency in package.json; used via CSS config, not direct JS import. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped org package @pelatform/ui; not a typosquat of joi — coincidental Levenshtein match. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.2.2 | 1 / 7 | |
| 2.2.1 | 1 / 7 | |
| 2.2.0 | 1 / 7 | |
| 2.1.1 | 1 / 7 | |
| 2.1.0 | 1 / 7 | |
| 1.6.0 | 32 / 9 | |
| 1.5.8 | 31 / 9 |
v2.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.