← Home

@jsreport/jsreport-cli

npm Repository Homepage

Command line interface for jsreport

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

Maintainers

pofiderbjrmatos

Keywords

jsreportclicommandsjsreport commands

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:dynamic-require AI (semgrep): CLI commander/plugin loader pattern in a well-established jsreport package; stable across versions. ai
provenance no-provenance AI (provenance): Established package; lack of provenance is common and not a risk signal here. ai

Versions (showing 4 of 4)

Version Deps Published
4.2.1 18 / 16
4.2.0 18 / 16
4.1.2 18 / 16
4.1.1 18 / 16

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
INFO No provenance attestation provenance

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

v4.1.2

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