@iconify-vue/gg
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:pg | AI (typosquat): Scoped @iconify-vue package; 'gg' is an icon set name, not a typosquat of 'pg'. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Same rationale; icon set name under established @iconify-vue scope. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Same rationale; icon set name under established @iconify-vue scope. | ai | |
| phantom-deps | phantom-dep:@iconify/css-vue | AI (phantom-deps): Icon library; peer/config reference to @iconify/css-vue is expected and not a real phantom dep. | ai |
v1.0.3
2 findingsPackage name '@iconify-vue/gg' is 1 edit(s) away from popular package 'pg'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
2 findingsPackage name '@iconify-vue/gg' is 1 edit(s) away from popular package 'pg'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
2 findingsPackage name '@iconify-vue/gg' is 1 edit(s) away from popular package 'pg'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.