@jsreport/jsreport-html-embedded-in-docx
jsreport recipe embedding output html into the docx
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Decodes docx content buffer as part of normal recipe processing; not a payload concern. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 4.2.1 | 4 / 5 | |
| 4.2.0 | 4 / 5 | |
| 4.1.5 | 4 / 5 | |
| 4.1.4 | 4 / 5 | |
| 4.1.3 | 4 / 5 | |
| 4.1.2 | 4 / 5 | |
| 4.1.1 | 4 / 5 |
v4.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.