@jsreport/office
Some helpers for office based jsreport recipes
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Legitimate jsreport sub-package; sparse README/keywords are expected for internal helper libraries. | ai | |
| phantom-deps | phantom-dep:zip | AI (phantom-deps): zip is a declared runtime dep used via config/archiver integration; phantom-dep heuristic fires on indirect usage patterns. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 4.2.1 | 8 / 3 | |
| 4.2.0 | 8 / 3 | |
| 4.1.5 | 8 / 3 | |
| 4.1.4 | 8 / 3 | |
| 4.1.3 | 8 / 3 | |
| 4.1.2 | 8 / 3 | |
| 4.1.1 | 8 / 3 | |
| 4.1.0 | 8 / 3 | |
| 4.0.0 | 8 / 3 |
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.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.