@fortawesome/fontawesome-svg-core
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 | obfuscated-file:plugins.es.js | AI (source-diff): plugins.es.js is a standard Babel-bundled ES module output for Font Awesome's plugins API. Long lines are from bundling, not obfuscation. Legitimate addition by trusted publisher. | ai | |
| dependencies | unvetted-dep:@fortawesome/fontawesome-common-types | AI (dependencies): First-party Font Awesome dependency in the same namespace; consistently used across all versions of this package. Not a third-party risk. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): Postinstall runs 'node attribution.js', a benign attribution/license notice script consistent with Font Awesome's documented behavior across all versions. | ai | |
| provenance | no-provenance | AI (provenance): Font Awesome is a well-established package with a long track record; lack of Sigstore provenance is not a concern for this publisher. | ai |
Versions (showing 49 of 49)
| 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 | |
| 6.5.1 | 1 / 0 | |
| 6.5.0 | 1 / 0 | |
| 6.4.0 | 1 / 0 | |
| 6.3.0 | 1 / 0 | |
| 6.2.1 | 1 / 0 | |
| 6.1.2 | 1 / 0 | |
| 6.1.1 | 1 / 0 | |
| 1.3.0 | 1 / 0 | |
| 1.2.36 | 1 / 0 | |
| 1.2.32 | 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 |
v7.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.
v7.0.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.
v7.0.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.
v6.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.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.
v6.7.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.
v6.6.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.
v6.5.1
2 findingsScript: node attribution.js
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.5.0
2 findingsScript: node attribution.js
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.0
2 findingsScript: node attribution.js
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.0
2 findingsScript: node attribution.js
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.1
2 findingsScript: node attribution.js
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.2
2 findingsScript: node attribution.js
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.1
2 findingsScript: node attribution.js
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.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.
v1.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.