@yyc3/ui
YYC³ AI Family UI 组件库 — 即拉即用的 React AI 智能系统 UI 组件 + 56个shadcn/ui标准组件
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped package @yyc3/ui; Levenshtein match to uuid is coincidental, not an impersonation. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @yyc3/ui; Levenshtein match to pg is coincidental, not an impersonation. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @yyc3/ui; Levenshtein match to qs is coincidental, not an impersonation. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @yyc3/ui; Levenshtein match to joi is coincidental, not an impersonation. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped package @yyc3/ui; Levenshtein match to yup is coincidental, not an impersonation. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 2.0.2 | 15 / 16 | |
| 2.0.1 | 15 / 16 | |
| 2.0.0 | 15 / 16 | |
| 1.1.1 | 1 / 11 | |
| 1.1.0 | 1 / 11 | |
| 1.0.2 | 1 / 11 | |
| 1.0.1 | 1 / 11 | |
| 1.0.0 | 1 / 11 |
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.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.