← Home

geist

npm Repository Homepage
14
Versions
—
License
No
Install Scripts
Attested
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation (unverified) npm registry signatures No source commit

Maintainers

vercel-release-botzeit-bot

Keywords

geistgeist monogeist sansgeist pixelvercel font

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 14 of 14)

Version Deps Published
1.7.2 0 / 1
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
1.3.1 0 / 0
1.3.0 0 / 0
1.2.2 0 / 0
1.2.1 0 / 0
1.2.0 0 / 0
1.1.0 0 / 0
1.0.1 0 / 0
1.0.0 1 / 0

v1.3.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.