pdf-lib
1
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
hopding
Keywords
pdf-libpdfdocumentcreatemodifycreationmodificationediteditingtypescriptjavascriptlibrary
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@pdf-lib/upng | AI (dependencies): @pdf-lib/upng is a first-party scoped package under the same @pdf-lib namespace maintained by the pdf-lib author; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@pdf-lib/standard-fonts | AI (dependencies): @pdf-lib/standard-fonts is a first-party scoped package under the same @pdf-lib namespace maintained by the pdf-lib author; not a third-party risk. | ai | |
| provenance | no-provenance | AI (provenance): pdf-lib is a mature, well-established package; lack of Sigstore provenance is common and not a meaningful risk signal here. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 1.17.1 | 4 / 22 |
v1.17.1
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.