@oinone/kunlun-vue-router
默认layout
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:@oinone/kunlun-vue-widget | AI (dependencies): Same-org monorepo dependency; consistent pattern across all @oinone packages. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all oinone packages; publisher does not use Sigstore attestation. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Part of established @oinone monorepo; sparse metadata is consistent across the namespace, not a spam indicator. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 7.2.2 | 1 / 7 | |
| 7.2.1 | 1 / 7 | |
| 7.2.0 | 1 / 7 | |
| 7.1.0 | 1 / 7 | |
| 6.4.11 | 1 / 10 | |
| 6.4.10 | 1 / 10 | |
| 6.4.9 | 1 / 10 | |
| 6.4.8 | 1 / 10 | |
| 6.4.7 | 1 / 10 | |
| 6.4.6 | 1 / 10 | |
| 6.4.5 | 1 / 10 | |
| 6.4.4 | 1 / 10 | |
| 6.4.3 | 1 / 10 | |
| 6.4.2 | 1 / 10 | |
| 6.4.1 | 1 / 10 | |
| 6.4.0 | 1 / 10 | |
| 6.3.13 | 1 / 10 | |
| 6.3.12 | 1 / 10 | |
| 6.3.11 | 1 / 10 | |
| 6.3.10 | 1 / 10 | |
| 6.3.9 | 1 / 10 | |
| 6.3.8 | 1 / 10 | |
| 6.3.7 | 1 / 10 | |
| 6.3.6 | 1 / 10 | |
| 6.3.5 | 1 / 10 | |
| 6.3.4 | 1 / 10 |
v7.2.2
1 finding[Accepted risk] 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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.