@oinone/kunlun-router
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@types/page | AI (dependencies): @types/page is the standard TypeScript types for the 'page' routing lib already in deps; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/page | AI (phantom-deps): @types/page is a type-only dep; not directly imported at runtime is expected for TypeScript type packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped monorepo package; missing metadata is a consistent pattern across the oinone publisher's packages, not a spam indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent with oinone monorepo publishing pattern; not a malice indicator. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 7.2.1 | 2 / 3 | |
| 7.2.0 | 2 / 3 | |
| 7.1.0 | 2 / 3 | |
| 6.4.4 | 3 / 2 | |
| 6.4.2 | 3 / 2 | |
| 6.4.0 | 3 / 2 | |
| 6.3.2 | 3 / 2 | |
| 6.3.1 | 3 / 2 |
v7.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.0
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.