@cantoo/pdf-lib
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:dist/pdf-lib.esm.js | AI (source-diff): Long encoded strings are base64-compressed PDF font data (e.g. CourierBoldCompressed) decoded via pako inflate — standard and documented behavior for this PDF library. | ai | |
| source-diff | encoded-string-file:dist/pdf-lib.esm.min.js | AI (source-diff): Minified bundle contains base64 encode/decode utilities and compressed font data — expected for a PDF manipulation library, not malicious. | ai | |
| source-diff | encoded-string-file:dist/pdf-lib.js | AI (source-diff): Long encoded strings are base64-compressed PDF font data decoded via pako inflate — standard behavior for this PDF library. | ai | |
| source-diff | encoded-string-file:dist/pdf-lib.min.js | AI (source-diff): Minified UMD bundle contains base64 utilities and compressed font data — expected for a PDF manipulation library, not malicious. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 107 versions and 1800+ day history; lack of Sigstore provenance is common and not a risk signal for this package. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 2.7.1 | 7 / 30 | |
| 2.7.0 | 7 / 30 | |
| 2.6.5 | 7 / 30 | |
| 2.6.4 | 7 / 30 | |
| 2.6.3 | 7 / 30 | |
| 2.6.2 | 7 / 30 | |
| 2.6.1 | 7 / 30 | |
| 2.6.0 | 7 / 30 | |
| 2.5.3 | 7 / 30 | |
| 2.5.2 | 7 / 30 | |
| 2.5.1 | 7 / 30 | |
| 2.5.0 | 7 / 30 | |
| 2.4.5 | 7 / 30 | |
| 2.4.4 | 7 / 30 | |
| 2.4.3 | 7 / 30 | |
| 2.4.2 | 7 / 30 | |
| 2.4.1 | 7 / 30 | |
| 2.4.0 | 6 / 31 |
v2.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.4
5 findingsModified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.