← Home

@jsreport/jsreport-pdf-utils

jsreport extension providing pdf operations like merge or concatenation

11
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

pofiderbjrmatos

Keywords

jsreportpdf

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 11 of 11)

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
4.3.0 7 / 15
4.2.2 7 / 15
4.2.1 7 / 15
4.2.0 7 / 15

v4.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.2.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.2.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.

v4.2.0

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.