@iconify-svelte/vs
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped iconify icon-set package; /vs suffix coincidentally close to 'qs' but no impersonation intent. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Same rationale; scoped icon-set package with no relation to 'pg'. | ai | |
| phantom-deps | phantom-dep:@iconify/css-svelte | AI (phantom-deps): Svelte component package; dependency used via Svelte config/preprocessor, not direct JS import. | ai |
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
2 findingsPackage name '@iconify-svelte/vs' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.