@sitecore-jss/sitecore-jss-react-native
This module is provided as a part of Sitecore JavaScript Rendering SDK (JSS). It contains the integration for React Native (services & components).
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:react-native-svg-uri | AI (dependencies): Known React Native SVG rendering package; consistent with this package's documented purpose across versions. | ai | |
| dependencies | unvetted-dep:react-native-htmlview | AI (dependencies): Known React Native HTML rendering package; consistent with this package's documented purpose across versions. | ai | |
| phantom-deps | phantom-dep:react-native-svg | AI (phantom-deps): react-native-svg is a platform-specific binary dep; not directly imported in JS is expected for this package type. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Sitecore JSS packages historically have sparse READMEs/keywords; not indicative of spam. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 22.12.1 | 5 / 25 | |
| 22.9.1 | 5 / 25 | |
| 22.9.0 | 5 / 25 | |
| 22.8.0 | 5 / 25 | |
| 22.6.0 | 5 / 25 | |
| 21.11.0 | 5 / 25 | |
| 21.10.1 | 5 / 25 |
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.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.