pdfkit
A PDF generation library for Node.js
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:js/pdfkit.standalone.js | AI (source-diff): Embedded ICC sRGB color profile for PDF/A support; not obfuscated payload. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding in pdfkit is used for hardcoded PDF binary constants (e.g., CIDSet bitmaps), not dynamic payloads. Stable false positive for this package. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding is used to parse data URIs for image embedding — standard PDF library functionality, not obfuscation. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 0.19.0 | 6 / 23 | |
| 0.18.0 | 6 / 23 | |
| 0.17.2 | 5 / 24 | |
| 0.17.1 | 5 / 24 |
v0.19.0
2 findingsModified file contains 7 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.