@oinone/kunlun-vue-admin-base
中后台平台工程入口和默认实现
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): Internal monorepo sub-package; thin entry point and sparse metadata are expected for this package family. | ai | |
| phantom-deps | phantom-dep:file-saver | AI (phantom-deps): Declared runtime dep used transitively via config; phantom-dep heuristic is a false positive here. | ai | |
| phantom-deps | phantom-dep:@wangeditor/editor-for-vue | AI (phantom-deps): Same pattern — declared dep referenced in config files; stable false positive for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 7.2.2 | 13 / 25 | |
| 7.2.1 | 13 / 25 | |
| 7.2.0 | 13 / 25 | |
| 6.4.11 | 13 / 25 | |
| 6.4.10 | 13 / 25 |
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.
v6.4.11
1 findingPackage 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.