@oinone/kunlun-dependencies
2
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
oinone
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): Intentional umbrella/aggregation package; tiny payload and empty entry point are by design. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Aggregation package; missing description is cosmetic, not a risk signal. | ai | |
| phantom-deps | phantom-dep:@oinone/kunlun-cache | AI (phantom-deps): Same-org dep in an umbrella package; not imported directly by design. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common; no other risk signals warrant blocking on this alone. | ai |
v7.2.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.7
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.