@oinone/kunlun-vue-ui-common
内置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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:icons/iconfont-deprecated/iconfont.js | AI (source-diff): File is an SVG iconfont sprite bundle; long lines are SVG path data, not obfuscated code. | ai | |
| source-diff | obfuscated-file:icons/oinone-iconfont/iconfont.js | AI (source-diff): File is an SVG iconfont sprite bundle; long lines are SVG path data, not obfuscated code. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Part of oinone monorepo; missing metadata is a monorepo artifact, not spam. Stable across versions. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Used in upload event handler to evaluate user-configured template strings; consistent pattern for this package's upload utility. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): lodash declared as dependency; likely used transitively or in config — stable false positive for this package. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 7.2.2 | 2 / 9 | |
| 7.2.1 | 2 / 9 | |
| 7.2.0 | 2 / 9 | |
| 7.1.0 | 2 / 9 | |
| 6.4.11 | 2 / 9 | |
| 6.4.10 | 2 / 9 | |
| 6.4.9 | 2 / 9 | |
| 6.4.8 | 2 / 9 | |
| 6.4.7 | 2 / 9 | |
| 6.4.6 | 2 / 9 | |
| 6.4.5 | 2 / 9 | |
| 6.4.4 | 2 / 9 | |
| 6.4.3 | 2 / 9 | |
| 6.4.2 | 2 / 9 | |
| 6.4.1 | 2 / 9 | |
| 6.4.0 | 2 / 9 | |
| 6.3.13 | 2 / 9 | |
| 6.3.12 | 2 / 9 | |
| 6.3.11 | 2 / 9 | |
| 6.3.10 | 2 / 9 | |
| 6.3.9 | 2 / 9 | |
| 6.3.8 | 2 / 9 | |
| 6.3.7 | 2 / 9 | |
| 6.3.6 | 2 / 9 | |
| 6.3.5 | 2 / 9 | |
| 6.3.4 | 2 / 9 |
v7.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.
v7.1.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
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.9
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.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.6
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.
v6.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.