@wzyjs/uis
description
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:handlebars | AI (dependencies): Pinned to ^4.7.8 which is the patched version; no known unpatched CVEs in this range. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Growth explained by addition of multiple legitimate UI component modules (xyflow, pro-card, pro-form, dnd, etc.). | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase correlates directly with 7 new runtime deps and their corresponding component source files. | ai | |
| phantom-deps | phantom-dep:echarts | AI (phantom-deps): Declared as runtime dep for consumers; config-file-only reference is expected for a component library. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped UI component library @wzyjs/uis; not a typosquat of uuid. | ai | |
| phantom-deps | phantom-dep:rehype-starry-night | AI (phantom-deps): Declared as runtime dep for consumers; config-file-only reference is expected for a component library. | ai | |
| phantom-deps | phantom-dep:remark-toc | AI (phantom-deps): Declared as runtime dep for consumers; config-file-only reference is expected for a component library. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped UI component library @wzyjs/uis; not a typosquat of qs. | ai | |
| phantom-deps | phantom-dep:ali-oss | AI (phantom-deps): Declared as runtime dep for consumers; config-file-only reference is expected for a component library. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.3.36 | 26 / 7 | |
| 0.3.29 | 23 / 2 | |
| 0.3.28 | 23 / 2 | |
| 0.3.26 | 22 / 0 | |
| 0.3.23 | 22 / 0 | |
| 0.3.22 | 22 / 0 | |
| 0.3.18 | 22 / 0 | |
| 0.3.10 | 22 / 0 | |
| 0.3.9 | 22 / 0 | |
| 0.3.8 | 22 / 0 |
v0.3.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.