@postxl/ui-components
PostXL UI component library - Radix UI primitives with Tailwind CSS styling
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:use-local-storage-state | AI (phantom-deps): Config-file reference in UI component library; stable pattern. | ai | |
| dependencies | unvetted-dep:@radix-ui/react-avatar | AI (dependencies): Radix UI is a well-known, widely-trusted primitive library; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@radix-ui/react-select | AI (dependencies): Radix UI is a well-known, widely-trusted primitive library; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@radix-ui/react-hover-card | AI (dependencies): Radix UI is a well-known, widely-trusted primitive library; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:use-local-storage-state | AI (dependencies): use-local-storage-state is a well-established utility with broad ecosystem usage; low risk. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-context | AI (phantom-deps): Radix UI internal sub-package; used transitively by other @radix-ui deps, not a real phantom dep concern. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-checkbox | AI (phantom-deps): Declared in package.json dependencies; likely referenced indirectly via bundled components. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.8.0 | 44 / 26 | |
| 1.7.1 | 44 / 26 | |
| 1.5.3 | 44 / 26 | |
| 1.3.5 | 40 / 22 | |
| 1.0.0 | 40 / 22 |
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.