@foliojs-fork/pdfkit
1
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
liborm85
Keywords
pdfpdf writerpdf generatorgraphicsdocumentvector
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding is used for hardcoded PDF spec constants (e.g., CIDSet bitmaps), not dynamic/user-controlled data. Stable false positive for a PDF generation library. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding is used to parse data URIs for embedded images — standard and expected behavior for a PDF generation library. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 0.15.3 | 5 / 23 |
v0.15.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.