← Home

@jsreport/jsreport-core

javascript based business reporting

5
Versions
LGPL
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

pofiderbjrmatos

Keywords

reportbusinessjavascript

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:base64-decode AI (semgrep): Used in blob storage write path to decode user-supplied content; not obfuscation. ai
semgrep semgrep:hex-decode AI (semgrep): Used in encryption/decryption module for AES-GCM; standard crypto pattern. ai
semgrep semgrep:dynamic-require AI (semgrep): Used to load config files by path in extension discovery; documented framework pattern. ai
phantom-deps phantom-dep:listener-collection AI (phantom-deps): Likely used transitively or via re-export in this framework package. ai
phantom-deps phantom-dep:@jsreport/serializator AI (phantom-deps): Same org scope; likely used indirectly or in worker boundary serialization. ai

Versions (showing 5 of 5)

Version Deps Published
4.10.0 38 / 7
4.9.0 39 / 7
4.8.0 39 / 7
4.7.1 39 / 7
4.7.0 39 / 7

v4.10.0

1 finding
LOW No provenance attestation provenance

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

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

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

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