← Home

fontkitten

npm Repository Homepage
20
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

delucis

Keywords

opentypefonttypographyemojiglyph

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher changed from delucis to GitHub Actions as part of a CI/CD migration; SLSA attestation confirms the publish originates from the official repo. This is a stable, expected pattern for this package. ai
provenance missing-githead AI (provenance): gitHead absence is explained by the GitHub Actions publish flow; SLSA provenance attestation provides stronger commit-level traceability than gitHead alone. ai
provenance no-provenance AI (provenance): fontkitten is a legitimate font utility library; lack of Sigstore provenance is a process gap, not a security risk for this package. ai

Versions (showing 20 of 20)

Version Deps Published
1.0.3 1 / 3
1.0.2 1 / 3
1.0.1 1 / 3
1.0.0 1 / 4
0.0.16 1 / 4
0.0.15 1 / 4
0.0.14 1 / 4
0.0.13 1 / 4
0.0.12 1 / 4
0.0.11 1 / 4
0.0.10 1 / 4
0.0.9 2 / 4
0.0.8 2 / 4
0.0.7 3 / 5
0.0.6 3 / 5
0.0.5 4 / 5
0.0.4 4 / 3
0.0.3 4 / 3
0.0.2 4 / 3
0.0.1 5 / 6

v1.0.3

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.0.16

3 findings
HIGH Missing gitHead — previous versions had it provenance

This 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.

HIGH Publisher changed: delucis → GitHub Actions (on 2025-11-18) provenance

This version was published by a different npm account than previous versions on 2025-11-18. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.0.2

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.