@expo-google-fonts/font-directory
A directory of metadata about the fonts available in `expo-google-fonts`
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 51 of 85)
| Version | Deps | Published |
|---|---|---|
| 0.4.74 | 0 / 0 | |
| 0.4.73 | 0 / 0 | |
| 0.4.72 | 0 / 0 | |
| 0.4.70 | 0 / 0 | |
| 0.4.69 | 0 / 0 | |
| 0.4.68 | 0 / 0 | |
| 0.4.67 | 0 / 0 | |
| 0.4.66 | 0 / 0 | |
| 0.4.65 | 0 / 0 | |
| 0.4.64 | 0 / 0 | |
| 0.4.63 | 0 / 0 | |
| 0.4.62 | 0 / 0 | |
| 0.4.61 | 0 / 0 | |
| 0.4.60 | 0 / 0 | |
| 0.4.59 | 0 / 0 | |
| 0.4.58 | 0 / 0 | |
| 0.4.57 | 0 / 0 | |
| 0.4.56 | 0 / 0 | |
| 0.4.55 | 0 / 0 | |
| 0.4.54 | 0 / 0 | |
| 0.4.53 | 0 / 0 | |
| 0.4.52 | 0 / 0 | |
| 0.4.51 | 0 / 0 | |
| 0.4.50 | 0 / 0 | |
| 0.4.49 | 0 / 0 | |
| 0.4.48 | 0 / 0 | |
| 0.4.47 | 0 / 0 | |
| 0.4.46 | 0 / 0 | |
| 0.4.45 | 0 / 0 | |
| 0.4.44 | 0 / 0 | |
| 0.4.42 | 0 / 0 | |
| 0.4.41 | 0 / 0 | |
| 0.4.40 | 0 / 0 | |
| 0.4.39 | 0 / 0 | |
| 0.4.38 | 0 / 0 | |
| 0.4.37 | 0 / 0 | |
| 0.4.36 | 0 / 0 | |
| 0.4.35 | 0 / 0 | |
| 0.4.34 | 0 / 0 | |
| 0.4.33 | 0 / 0 | |
| 0.4.32 | 0 / 0 | |
| 0.4.31 | 0 / 0 | |
| 0.4.30 | 0 / 0 | |
| 0.4.29 | 0 / 0 | |
| 0.4.28 | 0 / 0 | |
| 0.4.27 | 0 / 0 | |
| 0.4.26 | 0 / 0 | |
| 0.4.25 | 0 / 0 | |
| 0.4.24 | 0 / 0 | |
| 0.4.23 | 0 / 0 | |
| 0.4.22 | 0 / 0 |
v0.4.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.72
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 (jake7) than the most recent previously approved version (kadikraman) on 2026-07-15, but jake7 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.