← Home

@oinone/kunlun-vue-ui-mobile-vant

npm

内置ui组件库

13
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.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@vant/compat AI (dependencies): @vant/compat is the official Vant compatibility shim; expected dependency for a Vant-based UI package. ai
bogus-package bogus-package AI (bogus-package): Scoped monorepo package from established oinone publisher; missing metadata is consistent across their package family. ai
semgrep semgrep:api-obfuscation-reflect AI (semgrep): Reflect.get used only to fetch window.translate for i18n; not obfuscation or evasion. ai
phantom-deps phantom-dep:@vant/compat AI (phantom-deps): @vant/compat is a declared runtime dep; phantom-dep heuristic fires because it's referenced in config, not direct imports. ai

Versions (showing 13 of 13)

Version Deps Published
7.2.1 4 / 10
7.2.0 4 / 10
7.1.0 4 / 10
6.4.6 1 / 9
6.4.5 1 / 9
6.4.4 1 / 9
6.4.3 1 / 9
6.4.2 1 / 9
6.4.1 1 / 9
6.4.0 1 / 9
6.3.3 1 / 9
6.3.2 1 / 9
6.3.1 1 / 9

v7.2.1

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.

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.

v7.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.4.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.4.5

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.4.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.4.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.4.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.4.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.4.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.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.3.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.3.1

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.