@jsreport/jsreport-pdf-utils
jsreport extension providing pdf operations like merge or concatenation
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 |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Decodes a PDF signing certificate buffer — legitimate crypto use, not payload obfuscation. | ai | |
| phantom-deps | phantom-dep:node-forge | AI (phantom-deps): node-forge is a declared dependency used by the signing subsystem; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:lodash.omit | AI (phantom-deps): Declared dependency; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:parse-color | AI (phantom-deps): Declared dependency; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@jsreport/node-signpdf | AI (phantom-deps): Same-org declared dependency used for PDF signing; phantom-dep heuristic false positive. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 4.5.4 | 7 / 15 | |
| 4.5.3 | 7 / 15 | |
| 4.5.2 | 7 / 15 | |
| 4.5.1 | 7 / 15 | |
| 4.5.0 | 7 / 15 | |
| 4.4.1 | 7 / 15 | |
| 4.4.0 | 7 / 15 |
v4.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.2
2 findingsThis version was published by a different npm account than previous versions on 2026-01-29. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.