@rnx-kit/tools-react-native
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 |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Fires on require(rncli) where rncli is a resolved path to @react-native-community/cli — intentional plugin-loader pattern stable across versions. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 2.3.7 | 3 / 11 | |
| 2.3.5 | 3 / 11 | |
| 2.3.4 | 3 / 12 | |
| 2.3.3 | 2 / 12 | |
| 2.3.2 | 1 / 12 | |
| 2.3.1 | 1 / 12 | |
| 2.3.0 | 1 / 12 | |
| 2.2.0 | 1 / 12 |
v2.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.