@oinone/kunlun-engine
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 |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): Used only in scripts/check-keyword.js, a dev lint helper not shipped as runtime code. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads local package.json by resolved path in a postpublish dev script; not a runtime concern. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get/set used for ORM field mapping in src/helper/field.ts; standard TypeScript pattern, not obfuscation. | ai | |
| phantom-deps | phantom-dep:@oinone/kunlun-cache | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic unreliable for re-exported org packages. | ai | |
| phantom-deps | phantom-dep:@oinone/kunlun-config | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic unreliable for re-exported org packages. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 7.2.1 | 17 / 1 | |
| 7.2.0 | 17 / 1 | |
| 7.1.0 | 17 / 1 | |
| 6.4.2 | 17 / 28 | |
| 6.4.1 | 17 / 28 | |
| 6.4.0 | 17 / 28 | |
| 6.3.3 | 17 / 28 | |
| 6.3.2 | 17 / 28 | |
| 6.3.1 | 17 / 28 |
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.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.