@iconify/vue
2
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
cyberalien
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:vite | AI (typosquat): @iconify/vue is the legitimate Iconify Vue component, not a typosquat of vite. Scoped package under well-known @iconify namespace; edit-distance match is a false positive. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): @iconify/vue is the legitimate Iconify Vue component, not a typosquat of yup. Scoped package under well-known @iconify namespace; edit-distance match is a false positive. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established monorepo package (47 versions, 2196 days old); documentation lives on iconify.design. Short README and no keywords are cosmetic, not indicative of spam. | ai |
v5.0.1
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.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.