@oinone/kunlun-vue-ui
内置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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Umbrella/meta package pattern; empty index.ts and missing README are expected for this package type. | ai | |
| phantom-deps | phantom-dep:xe-utils | AI (phantom-deps): Transitive dep re-exported for consumers; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:sortablejs | AI (phantom-deps): Transitive dep re-exported for consumers; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:vuedraggable | AI (phantom-deps): Declared as peerDependency and re-exported; not directly imported in source is expected for this package. | ai | |
| phantom-deps | phantom-dep:vue3-smooth-dnd | AI (phantom-deps): UI component dependency re-exported via config; phantom detection is a false positive here. | ai | |
| phantom-deps | phantom-dep:vue3-draggable-resizable | AI (phantom-deps): UI component dependency re-exported via config; phantom detection is a false positive here. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 7.2.2 | 10 / 7 | |
| 7.2.1 | 10 / 7 | |
| 7.2.0 | 10 / 7 | |
| 6.4.11 | 9 / 7 | |
| 6.3.8 | 9 / 7 | |
| 6.3.5 | 9 / 7 |
v7.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.