@oinone/kunlun-vue-mobile-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 |
|---|---|---|---|---|
| source-diff | net-exec-file:dist/oinone-kunlun-vue-mobile-base.esm.js | AI (source-diff): Rollup-compiled ESM bundle of a Vue UI framework; network+exec pattern is from legitimate framework code, not malware. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo component; missing README/repo/keywords are expected for private-style scoped packages in this org. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): lodash is a common transitive/config-level dep in monorepos; stable false positive for this package. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Used to evaluate label expressions from config, not remote/user-controlled arbitrary code; stable pattern in this package. | ai | |
| phantom-deps | phantom-dep:@wangeditor/editor-for-vue | AI (phantom-deps): Declared as runtime dep and used via config/re-export; phantom-dep heuristic fires on indirect usage patterns. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 7.2.2 | 9 / 22 | |
| 7.2.1 | 9 / 22 | |
| 7.2.0 | 9 / 22 | |
| 7.1.0 | 9 / 22 | |
| 6.4.6 | 9 / 22 | |
| 6.4.5 | 9 / 22 | |
| 6.4.4 | 9 / 22 | |
| 6.4.3 | 9 / 22 | |
| 6.4.2 | 9 / 22 | |
| 6.4.1 | 9 / 22 | |
| 6.4.0 | 9 / 22 | |
| 6.3.3 | 9 / 22 | |
| 6.3.2 | 9 / 22 | |
| 6.3.1 | 9 / 22 |
v7.2.2
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package 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.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.