@react-native-community/cli
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-community/cli is a well-known React Native tool with no relation to 'joi'. Levenshtein match is a false positive due to scoped name comparison. | ai | |
| dependencies | unvetted-dep:@react-native-community/cli-clean | AI (dependencies): Sibling monorepo package co-released at the same version; expected dependency for this package. | ai | |
| dependencies | unvetted-dep:@react-native-community/cli-types | AI (dependencies): Sibling monorepo package co-released at the same version; expected dependency for this package. | ai | |
| dependencies | unvetted-dep:@react-native-community/cli-config | AI (dependencies): Sibling monorepo package co-released at the same version; expected dependency for this package. | ai | |
| dependencies | unvetted-dep:@react-native-community/cli-doctor | AI (dependencies): Sibling monorepo package co-released at the same version; expected dependency for this package. | ai | |
| dependencies | unvetted-dep:@react-native-community/cli-server-api | AI (dependencies): Sibling monorepo package co-released at the same version; expected dependency for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Well-known React Native CLI tool; README/keyword signals are cosmetic and not indicative of spam or low-value package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 20.1.3 | 15 / 7 | |
| 20.1.2 | 15 / 7 | |
| 20.1.1 | 15 / 7 | |
| 20.1.0 | 15 / 7 | |
| 20.0.2 | 15 / 7 | |
| 20.0.1 | 15 / 7 | |
| 20.0.0 | 15 / 7 | |
| 19.1.2 | 15 / 7 | |
| 18.0.1 | 15 / 7 | |
| 17.0.1 | 15 / 7 |
v20.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.