← Home

@react-pdf/font

6
Versions
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

diegomura

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from manual to GitHub Actions CI/CD publishing with SLSA provenance; expected for this repo. ai
typosquat typosquat.levenshtein:got AI (typosquat): Scoped package @react-pdf/font is not a typosquat of 'got'; Levenshtein match is a false positive for this package. ai
phantom-deps phantom-dep:@react-pdf/types AI (phantom-deps): Same-org type-only dependency; not directly imported in source but legitimately declared for type resolution. ai

Versions (showing 6 of 6)

Version Deps Published
4.0.8 4 / 2
4.0.7 4 / 2
4.0.6 4 / 2
4.0.5 4 / 2
4.0.4 4 / 2
4.0.3 4 / 2

v4.0.8

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.

v4.0.7

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.

v4.0.5

2 findings
HIGH Publisher changed: diegomura → GitHub Actions (on 2026-04-04) provenance

This version was published by a different npm account than previous versions on 2026-04-04. 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.

v4.0.4

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.

v4.0.3

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.