@fortawesome/fontawesome-common-types
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 |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): Font Awesome's attribution.js prints a license notice at install time; this postinstall has been present across many versions and is benign. | ai | |
| provenance | no-provenance | AI (provenance): Informational only; Font Awesome predates Sigstore provenance adoption. No security concern. | ai |
Versions (showing 51 of 60)
| Version | Deps | Published |
|---|---|---|
| 7.2.0 | 0 / 0 | |
| 7.1.0 | 0 / 0 | |
| 7.0.1 | 0 / 0 | |
| 7.0.0 | 0 / 0 | |
| 6.7.2 | 0 / 0 | |
| 6.7.1 | 0 / 0 | |
| 6.7.0 | 0 / 0 | |
| 6.6.0 | 0 / 0 | |
| 6.5.1 | 0 / 0 | |
| 6.5.0 | 0 / 0 | |
| 6.4.2 | 0 / 0 | |
| 6.4.0 | 0 / 0 | |
| 6.3.0 | 0 / 0 | |
| 6.1.1 | 0 / 0 | |
| 6.1.0 | 0 / 0 | |
| 0.3.0 | 0 / 0 | |
| 0.2.36 | 0 / 0 | |
| 0.2.35 | 0 / 0 | |
| 0.2.34 | 0 / 0 | |
| 0.2.32 | 0 / 0 | |
| 0.2.31 | 0 / 0 | |
| 0.2.30 | 0 / 0 | |
| 0.2.29 | 0 / 0 | |
| 0.2.28 | 0 / 0 | |
| 0.2.27 | 0 / 0 | |
| 0.2.26 | 0 / 0 | |
| 0.2.25 | 0 / 0 | |
| 0.2.24 | 0 / 0 | |
| 0.2.23 | 0 / 0 | |
| 0.2.22 | 0 / 0 | |
| 0.2.21 | 0 / 0 | |
| 0.2.20 | 0 / 0 | |
| 0.2.19 | 0 / 0 | |
| 0.2.18 | 0 / 0 | |
| 0.2.17 | 0 / 0 | |
| 0.2.16 | 0 / 0 | |
| 0.2.15 | 0 / 0 | |
| 0.2.14 | 0 / 0 | |
| 0.2.13 | 0 / 0 | |
| 0.2.12 | 0 / 0 | |
| 0.2.11 | 0 / 0 | |
| 0.2.10 | 0 / 0 | |
| 0.2.9 | 0 / 0 | |
| 0.2.8 | 0 / 0 | |
| 0.2.7 | 0 / 0 | |
| 0.2.6 | 0 / 0 | |
| 0.2.5 | 0 / 0 | |
| 0.2.4 | 0 / 0 | |
| 0.2.3 | 0 / 0 | |
| 0.2.2 | 0 / 0 | |
| 0.2.1 | 0 / 0 |
v6.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.0
2 findingsScript: node attribution.js
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
2 findingsScript: node attribution.js
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.