@iconify/json
Hundreds of open source icon sets in IconifyJSON format
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:jsdom | AI (typosquat): Icon-data package unrelated to jsdom; edit-distance false positive. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Icon-data package unrelated to joi; edit-distance false positive. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 2.2.504 | 2 / 8 | |
| 2.2.503 | 2 / 8 | |
| 2.2.502 | 2 / 8 | |
| 2.2.501 | 2 / 8 |
v2.2.504
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.503
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.502
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.501
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.