@aplus-frontend/antdv
2
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
huimin2000rainiexxxhuazollieliulimoerasd517665931zxlin429kuguago
Keywords
vuevue3antdesignantdvueComponentcomponentcomponentsuiframeworkfrontend
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): 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 |
v2.2.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.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.