@jsreport/jsreport-assets
jsreport extension embedding static assets like fonts or helpers into the templates
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:enhanced-resolve | AI (phantom-deps): enhanced-resolve is listed in package.json dependencies; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 4.3.1 | 9 / 12 | |
| 4.3.0 | 9 / 12 | |
| 4.2.3 | 9 / 12 | |
| 4.2.2 | 9 / 12 | |
| 4.2.1 | 9 / 12 | |
| 4.2.0 | 9 / 12 | |
| 4.1.1 | 9 / 12 | |
| 4.1.0 | 9 / 12 | |
| 4.0.2 | 9 / 12 | |
| 4.0.1 | 9 / 12 | |
| 4.0.0 | 9 / 12 |
v4.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
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.