@jsreport/jsreport-docx
jsreport recipe rendering docx files
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): exifreader is a legitimate EXIF parsing library; addition is consistent with image handling in a docx renderer. | ai | |
| dependencies | unvetted-dep:exifreader | AI (dependencies): Used for reading image metadata in docx image handling; purpose-appropriate for this package. | ai | |
| dependencies | unvetted-dep:style-attr | AI (dependencies): CSS style attribute parsing utility; fits docx rendering use case. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding is used for image data URI parsing in docx rendering — benign and stable for this package. | ai | |
| dependencies | unvetted-dep:string-replace-async | AI (dependencies): Async string replacement utility; fits template rendering use case. | ai | |
| dependencies | unvetted-dep:js-excel-date-convert | AI (dependencies): Excel date conversion utility; fits docx/Office document rendering use case. | ai | |
| dependencies | unvetted-dep:parse-css-sides | AI (dependencies): CSS sides parsing utility; fits docx layout/styling use case. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 4.10.2 | 16 / 11 | |
| 4.10.1 | 16 / 11 | |
| 4.10.0 | 16 / 11 | |
| 4.9.0 | 15 / 11 | |
| 4.8.0 | 15 / 11 |
v4.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.