@jsreport/jsreport-express
jsreport extension adding API
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package; provenance absence is common and not a disqualifier here. | ai | |
| license | uncommon-license:LGPL | AI (license): LGPL is a well-known copyleft license; stable for this package. | ai | |
| dependencies | unvetted-dep:simple-odata-server | AI (dependencies): simple-odata-server is a stable, long-standing dependency of this package for OData API support; not a new or suspicious addition. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 4.3.2 | 12 / 10 | |
| 4.3.1 | 12 / 10 | |
| 4.3.0 | 13 / 10 | |
| 4.2.3 | 13 / 10 | |
| 4.2.2 | 13 / 10 | |
| 4.2.1 | 13 / 10 |
v4.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.