@aetherstack/ui
2
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
bogdan.m
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped package @aetherstack/ui; 'ui' suffix matching 'uuid' is a false positive, not an impersonation attempt. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package; 'ui' vs 'pg' is a spurious Levenshtein match, not a typosquat. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package; 'ui' vs 'qs' is a spurious Levenshtein match, not a typosquat. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package; 'ui' vs 'joi' is a spurious Levenshtein match, not a typosquat. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped package; 'ui' vs 'yup' is a spurious Levenshtein match, not a typosquat. | ai | |
| phantom-deps | phantom-dep:clsx | AI (phantom-deps): clsx is a declared runtime dep used in Tailwind utility patterns; config-file-only detection is a known false positive for UI libraries. | ai | |
| phantom-deps | phantom-dep:tailwind-merge | AI (phantom-deps): tailwind-merge is a declared runtime dep; config-file-only detection is a known false positive for shadcn-style UI libraries. | ai | |
| phantom-deps | phantom-dep:date-fns | AI (phantom-deps): date-fns is a declared runtime dep used by react-day-picker calendar component; config-file detection is a false positive. | ai |
v0.2.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.