geist
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Vercel migrated from vercel-release-bot to GitHub Actions; SLSA provenance confirms CI publish. | ai | |
| provenance | missing-githead | AI (provenance): Artifact of GitHub Actions publish flow; SLSA attestation compensates. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Font package; infrequent updates are normal for this package. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): geist is Vercel's official branded font package, not a typosquat of jest. The name similarity is coincidental; these are entirely different package categories. | ai | |
| license | uncommon-license:SIL OPEN FONT LICENSE | AI (license): SIL Open Font License is the standard license for font packages; entirely appropriate and expected for this font family package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.7.1 | 0 / 1 | |
| 1.7.0 | 0 / 1 | |
| 1.5.1 | 0 / 0 | |
| 1.4.2 | 0 / 0 | |
| 1.4.1 | 0 / 0 |
v1.7.1
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-05-20. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.