@iconify-json/ion
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:koa | AI (typosquat): Scoped Iconify icon-set package; 'ion' is the IonIcons set name, not a typosquat. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped Iconify icon-set package; 'ion' is the IonIcons set name, not a typosquat. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped Iconify icon-set package; 'ion' is the IonIcons set name, not a typosquat. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped Iconify icon-set package; 'ion' is the IonIcons set name, not a typosquat. | ai |
v1.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.