@oinone/kunlun-vue-widget
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:api-obfuscation-reflect | AI (semgrep): Reflect.get/set used for standard property copying in widget hook result merging; not obfuscation. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Part of @oinone monorepo; missing metadata is consistent across all scoped packages in this family. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent pattern across all @oinone/kunlun-* packages; not a malware indicator. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 7.2.2 | 1 / 13 | |
| 7.2.1 | 1 / 13 | |
| 7.2.0 | 1 / 13 | |
| 7.1.0 | 1 / 13 | |
| 6.4.11 | 1 / 13 | |
| 6.4.10 | 1 / 13 | |
| 6.4.9 | 1 / 13 | |
| 6.4.8 | 1 / 13 | |
| 6.4.7 | 1 / 13 | |
| 6.4.6 | 1 / 13 | |
| 6.4.5 | 1 / 13 | |
| 6.4.4 | 1 / 13 | |
| 6.4.3 | 1 / 13 | |
| 6.4.2 | 1 / 13 | |
| 6.4.1 | 1 / 13 | |
| 6.4.0 | 1 / 13 | |
| 6.3.13 | 2 / 12 | |
| 6.3.12 | 2 / 12 | |
| 6.3.11 | 2 / 12 | |
| 6.3.10 | 2 / 12 | |
| 6.3.9 | 2 / 12 | |
| 6.3.8 | 2 / 12 | |
| 6.3.7 | 2 / 12 | |
| 6.3.6 | 2 / 12 | |
| 6.3.5 | 2 / 12 | |
| 6.3.4 | 2 / 12 |
v7.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.7
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.