@jsreport/jsreport-version-control
4
Versions
—
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.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 used to decode binary file patch content in version-control diff logic; not a payload obfuscation pattern. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 4.2.1 | 10 / 13 | |
| 4.2.0 | 10 / 13 | |
| 4.1.1 | 11 / 13 | |
| 4.1.0 | 11 / 13 |
v4.1.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.