← Home

@aplus-frontend/antdv

npm
9
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

huimin2000rainiexxxhuazollieliulimoerasd517665931kuguago

Keywords

vuevue3antdesignantdvueComponentcomponentcomponentsuiframeworkfrontend

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:api-obfuscation-reflect AI (semgrep): Standard Vue 3 Proxy/reactive pattern using Reflect.get; not obfuscation. ai
semgrep semgrep:dynamic-require AI (semgrep): Used in dev-only token statistic script to load style files by path; not in runtime code. ai
semgrep semgrep:child-process-import AI (semgrep): Only in commitizen.js dev tooling script, not shipped runtime code. ai

Versions (showing 9 of 9)

Version Deps Published
2.2.1 23 / 185
2.2.0 23 / 185
2.1.5 23 / 185
2.1.4 23 / 185
2.1.3 23 / 185
2.1.2 23 / 185
2.1.1 23 / 185
2.1.0 23 / 185
2.0.5 23 / 185

v2.2.1

1 finding
LOW No provenance attestation provenance

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

v2.1.4

1 finding
LOW No provenance attestation provenance

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

v2.1.3

1 finding
LOW No provenance attestation provenance

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

v2.1.2

1 finding
LOW No provenance attestation provenance

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

v2.1.1

1 finding
LOW No provenance attestation provenance

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

v2.1.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.

v2.0.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.