@knewbeing/ui
[](https://www.npmjs.com/package/@knewbeing/ui) [](./LICENSE)
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped UI library; name similarity to uuid is coincidental, not a typosquat. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped UI library; name similarity to pg is coincidental, not a typosquat. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped UI library; name similarity to qs is coincidental, not a typosquat. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped UI library; name similarity to joi is coincidental, not a typosquat. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped UI library; name similarity to yup is coincidental, not a typosquat. | ai | |
| phantom-deps | phantom-dep:@vueuse/core | AI (phantom-deps): @vueuse/core is listed in dependencies; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.1.1 | 1 / 3 | |
| 1.1.0 | 1 / 3 | |
| 1.0.3 | 1 / 3 | |
| 1.0.2 | 1 / 2 | |
| 1.0.1 | 1 / 2 | |
| 1.0.0 | 1 / 2 |
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
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.