@react-native-windows/cli
CLI to build and run React Native for Windows apps.
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @react-native-windows/cli is clearly not a typosquat of 'joi'; the Levenshtein comparison is a false positive due to the scoped name structure. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic requires in this CLI tool load project package.json and config files at runtime — standard CLI tool pattern, not arbitrary code execution. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): CLI tool that orchestrates React Native Windows builds legitimately uses child_process to run build commands. Expected and documented behavior. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 0.83.0 | 21 / 24 | |
| 0.82.1 | 21 / 24 | |
| 0.82.0 | 21 / 24 | |
| 0.80.0 | 21 / 24 | |
| 0.79.4 | 21 / 24 | |
| 0.79.3 | 21 / 24 | |
| 0.79.2 | 20 / 24 | |
| 0.79.1 | 20 / 24 | |
| 0.79.0 | 20 / 24 | |
| 0.78.10 | 21 / 24 | |
| 0.78.9 | 21 / 24 | |
| 0.78.8 | 21 / 24 | |
| 0.78.6 | 21 / 24 | |
| 0.78.5 | 21 / 24 | |
| 0.78.4 | 21 / 24 | |
| 0.78.3 | 20 / 24 | |
| 0.77.6 | 20 / 24 | |
| 0.77.5 | 20 / 24 | |
| 0.77.4 | 20 / 24 | |
| 0.76.9 | 20 / 24 | |
| 0.76.8 | 20 / 24 | |
| 0.76.7 | 20 / 24 | |
| 0.75.11 | 21 / 25 | |
| 0.75.10 | 21 / 25 | |
| 0.75.9 | 21 / 25 | |
| 0.74.14 | 21 / 25 | |
| 0.74.12 | 21 / 25 |
v0.83.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: microsoft1es.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.82.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: microsoft1es.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.82.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.80.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.79.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.79.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.79.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.79.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.79.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.78.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.78.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.78.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.78.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.78.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.78.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.78.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.77.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.77.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.77.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.76.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.75.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.74.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.74.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.