@ukic/fonts
Typography assets for @ukic components
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 3.2.14 | 0 / 7 | |
| 3.2.13 | 0 / 7 | |
| 3.2.12 | 0 / 7 | |
| 3.2.11 | 0 / 7 | |
| 3.2.7 | 0 / 7 | |
| 3.2.6 | 0 / 7 | |
| 3.2.5 | 0 / 7 | |
| 3.2.4 | 0 / 7 | |
| 3.2.3 | 0 / 7 | |
| 3.2.2 | 0 / 7 | |
| 3.2.1 | 0 / 7 | |
| 3.2.0 | 0 / 7 | |
| 3.1.0 | 0 / 7 |
v3.2.14
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (gchq-developer-299a) than the most recent previously approved version (gchq-developer-112) on 2026-05-28, but gchq-developer-299a is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.