@jsreport/jsreport-html-to-xlsx
jsreport recipe capable of converting html into excel
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 | dormant-publish | AI (publish-pattern): Established jsreport ecosystem package with trusted publisher; long dormancy reflects project cadence, not takeover indicators. | ai | |
| dependencies | unvetted-dep:@jsreport/office | AI (dependencies): Internal jsreport ecosystem dependency; expected for this package. | ai | |
| dependencies | unvetted-dep:chrome-page-eval | AI (dependencies): Known jsreport utility dep; stable across versions. | ai | |
| dependencies | unvetted-dep:phantom-page-eval | AI (dependencies): Known jsreport utility dep; stable across versions. | ai | |
| dependencies | unvetted-dep:@jsreport/html-to-xlsx | AI (dependencies): Core internal jsreport dependency; expected for this package. | ai | |
| dependencies | unvetted-dep:node.extend.without.arrays | AI (dependencies): Utility dep used consistently across jsreport packages. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 4.4.1 | 7 / 10 | |
| 4.4.0 | 7 / 10 | |
| 4.3.0 | 7 / 10 | |
| 4.2.4 | 7 / 10 | |
| 4.2.3 | 7 / 10 | |
| 4.2.2 | 7 / 10 | |
| 4.2.1 | 7 / 10 |
v4.4.0
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.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.