@foliojs-fork/pdfkit
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
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 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.15.3 | 5 / 23 | |
| 0.15.2 | 5 / 23 | |
| 0.15.1 | 5 / 23 | |
| 0.15.0 | 5 / 23 | |
| 0.14.0 | 4 / 23 | |
| 0.13.0 | 4 / 22 | |
| 0.12.3 | 4 / 22 | |
| 0.12.1 | 4 / 22 |
v0.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.