@fortawesome/free-solid-svg-icons
The iconic font, CSS, and SVG framework
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): Font Awesome icon packs grow with each release as new SVG icons are added. Large file counts are expected and benign for this package. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): Font Awesome's postinstall runs 'node attribution.js' to display license/attribution info — no network access or dangerous operations. Stable and documented for this package. | ai | |
| dependencies | unvetted-dep:@fortawesome/fontawesome-common-types | AI (dependencies): This is the canonical companion package for Font Awesome; it is always a legitimate dependency of this package across all versions. | ai | |
| provenance | no-provenance | AI (provenance): Established package with strong publisher track record; lack of Sigstore provenance is not a risk signal here. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 7.2.0 | 1 / 0 | |
| 7.1.0 | 1 / 0 | |
| 7.0.1 | 1 / 0 | |
| 7.0.0 | 1 / 0 | |
| 6.7.2 | 1 / 0 | |
| 6.7.1 | 1 / 0 | |
| 6.7.0 | 1 / 0 | |
| 6.6.0 | 1 / 0 | |
| 5.15.3 | 1 / 0 | |
| 5.15.2 | 1 / 0 | |
| 5.14.0 | 1 / 0 | |
| 5.13.1 | 1 / 0 | |
| 5.13.0 | 1 / 0 | |
| 5.12.1 | 1 / 0 | |
| 5.12.0 | 1 / 0 | |
| 5.11.2 | 1 / 0 | |
| 5.11.1 | 1 / 0 | |
| 5.11.0 | 1 / 0 | |
| 5.10.2 | 1 / 0 | |
| 5.10.1 | 1 / 0 | |
| 5.10.0 | 1 / 0 | |
| 5.9.0 | 1 / 0 | |
| 5.8.2 | 1 / 0 | |
| 5.8.1 | 1 / 0 | |
| 5.8.0 | 1 / 0 | |
| 5.7.2 | 1 / 0 | |
| 5.7.1 | 1 / 0 | |
| 5.7.0 | 1 / 0 | |
| 5.6.3 | 1 / 0 | |
| 5.6.2 | 1 / 0 | |
| 5.6.1 | 1 / 0 | |
| 5.6.0 | 1 / 0 | |
| 5.5.0 | 1 / 0 | |
| 5.4.2 | 1 / 0 | |
| 5.4.1 | 1 / 0 | |
| 5.4.0 | 1 / 0 | |
| 5.3.1 | 1 / 0 | |
| 5.3.0 | 1 / 0 | |
| 5.2.0 | 1 / 0 | |
| 5.1.1 | 1 / 0 | |
| 5.1.0 | 1 / 0 |
v5.15.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.15.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.