@sitecore-jss/sitecore-jss-rendering-host
This module is provided as a part of Sitecore JavaScript Rendering SDK (JSS). It contains the rendering host implementation.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:ngrok | AI (dependencies): ngrok is a standard tunneling tool used in rendering host dev workflows; expected for this package's purpose. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped Sitecore org package; sparse README/keywords are consistent across the JSS monorepo. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 22.12.1 | 7 / 17 | |
| 22.12.0 | 7 / 17 | |
| 22.11.0 | 7 / 17 | |
| 22.10.0 | 7 / 17 | |
| 22.9.1 | 7 / 17 | |
| 22.9.0 | 7 / 17 | |
| 22.8.0 | 7 / 17 | |
| 22.6.0 | 7 / 17 | |
| 21.11.0 | 7 / 16 | |
| 21.10.1 | 7 / 16 |
v22.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.