@things-factory/font-base
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Long-lived monorepo package; no provenance is consistent across all 995 versions. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Migration file loader pattern — requires files from a known directory, not user-controlled input. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 9.2.24 | 3 / 0 | |
| 9.2.19 | 3 / 0 | |
| 9.0.0 | 3 / 0 | |
| 8.0.88 | 3 / 0 | |
| 8.0.87 | 3 / 0 | |
| 8.0.64 | 3 / 0 | |
| 8.0.63 | 3 / 0 | |
| 6.4.10 | 3 / 0 | |
| 4.3.755 | 2 / 0 | |
| 4.3.743 | 2 / 0 | |
| 4.3.740 | 2 / 0 | |
| 4.3.738 | 2 / 0 | |
| 4.3.729 | 2 / 0 | |
| 4.3.689 | 2 / 0 |
v9.2.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.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.
v8.0.88
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.755
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.743
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.740
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.738
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.729
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.689
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.