@iconify-json/simple-icons
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
Versions (showing 100 of 106)
| Version | Deps | Published |
|---|---|---|
| 1.2.90 | 1 / 0 | |
| 1.2.89 | 1 / 0 | |
| 1.2.88 | 1 / 0 | |
| 1.2.87 | 1 / 0 | |
| 1.2.86 | 1 / 0 | |
| 1.2.85 | 1 / 0 | |
| 1.2.84 | 1 / 0 | |
| 1.2.83 | 1 / 0 | |
| 1.2.82 | 1 / 0 | |
| 1.2.81 | 1 / 0 | |
| 1.2.80 | 1 / 0 | |
| 1.2.79 | 1 / 0 | |
| 1.2.78 | 1 / 0 | |
| 1.2.77 | 1 / 0 | |
| 1.2.76 | 1 / 0 | |
| 1.2.75 | 1 / 0 | |
| 1.2.74 | 1 / 0 | |
| 1.2.73 | 1 / 0 | |
| 1.2.72 | 1 / 0 | |
| 1.2.71 | 1 / 0 | |
| 1.2.70 | 1 / 0 | |
| 1.2.69 | 1 / 0 | |
| 1.2.68 | 1 / 0 | |
| 1.2.67 | 1 / 0 | |
| 1.2.66 | 1 / 0 | |
| 1.2.65 | 1 / 0 | |
| 1.2.64 | 1 / 0 | |
| 1.2.63 | 1 / 0 | |
| 1.2.62 | 1 / 0 | |
| 1.2.61 | 1 / 0 | |
| 1.2.60 | 1 / 0 | |
| 1.2.59 | 1 / 0 | |
| 1.2.58 | 1 / 0 | |
| 1.2.57 | 1 / 0 | |
| 1.2.56 | 1 / 0 | |
| 1.2.55 | 1 / 0 | |
| 1.2.54 | 1 / 0 | |
| 1.2.53 | 1 / 0 | |
| 1.2.52 | 1 / 0 | |
| 1.2.51 | 1 / 0 | |
| 1.2.50 | 1 / 0 | |
| 1.2.49 | 1 / 0 | |
| 1.2.48 | 1 / 0 | |
| 1.2.47 | 1 / 0 | |
| 1.2.46 | 1 / 0 | |
| 1.2.45 | 1 / 0 | |
| 1.2.44 | 1 / 0 | |
| 1.2.43 | 1 / 0 | |
| 1.2.42 | 1 / 0 | |
| 1.2.41 | 1 / 0 | |
| 1.2.40 | 1 / 0 | |
| 1.2.39 | 1 / 0 | |
| 1.2.38 | 1 / 0 | |
| 1.2.37 | 1 / 0 | |
| 1.2.36 | 1 / 0 | |
| 1.2.35 | 1 / 0 | |
| 1.2.34 | 1 / 0 | |
| 1.2.33 | 1 / 0 | |
| 1.2.32 | 1 / 0 | |
| 1.2.31 | 1 / 0 | |
| 1.2.30 | 1 / 0 | |
| 1.2.29 | 1 / 0 | |
| 1.2.28 | 1 / 0 | |
| 1.2.27 | 1 / 0 | |
| 1.2.26 | 1 / 0 | |
| 1.2.25 | 1 / 0 | |
| 1.2.24 | 1 / 0 | |
| 1.2.23 | 1 / 0 | |
| 1.2.22 | 1 / 0 | |
| 1.2.21 | 1 / 0 | |
| 1.2.20 | 1 / 0 | |
| 1.2.19 | 1 / 0 | |
| 1.2.18 | 1 / 0 | |
| 1.2.17 | 1 / 0 | |
| 1.2.16 | 1 / 0 | |
| 1.2.15 | 1 / 0 | |
| 1.2.14 | 1 / 0 | |
| 1.2.13 | 1 / 0 | |
| 1.2.12 | 1 / 0 | |
| 1.2.11 | 1 / 0 | |
| 1.2.10 | 1 / 0 | |
| 1.2.9 | 1 / 0 | |
| 1.2.8 | 1 / 0 | |
| 1.2.7 | 1 / 0 | |
| 1.2.6 | 1 / 0 | |
| 1.2.5 | 1 / 0 | |
| 1.2.4 | 1 / 0 | |
| 1.2.3 | 1 / 0 | |
| 1.2.2 | 1 / 0 | |
| 1.2.1 | 1 / 0 | |
| 1.2.0 | 1 / 0 | |
| 1.1.115 | 1 / 0 | |
| 1.1.114 | 1 / 0 | |
| 1.1.113 | 1 / 0 | |
| 1.1.112 | 1 / 0 | |
| 1.1.111 | 1 / 0 | |
| 1.1.110 | 1 / 0 | |
| 1.1.109 | 1 / 0 | |
| 1.1.108 | 1 / 0 | |
| 1.1.107 | 1 / 0 |
v1.2.90
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.87
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.
v1.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.115
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.114
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.113
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.112
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.111
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.110
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.109
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.108
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.107
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.