@react-native-community/cli-platform-apple
This package is part of the [React Native CLI](../../README.md). It contains utilities for building reusable commands targeting Apple platforms.
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): szymonrybczak is a known, trusted React Native community contributor (515 approved packages). Publisher transition within the react-native-community org is expected and legitimate. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Signals are a spam-flagged co-maintainer (cpojer, a known Meta/React Native contributor) and missing keywords. Neither is a real risk for this well-established community CLI package. | ai |
Versions (showing 46 of 46)
| Version | Deps | Published |
|---|---|---|
| 20.1.3 | 5 / 1 | |
| 20.1.2 | 5 / 1 | |
| 20.1.1 | 5 / 1 | |
| 20.1.0 | 5 / 1 | |
| 20.0.2 | 5 / 1 | |
| 20.0.1 | 5 / 1 | |
| 20.0.0 | 5 / 1 | |
| 19.1.2 | 5 / 1 | |
| 19.1.1 | 5 / 1 | |
| 19.1.0 | 5 / 1 | |
| 19.0.0 | 5 / 1 | |
| 18.0.1 | 5 / 1 | |
| 18.0.0 | 5 / 1 | |
| 17.0.1 | 5 / 1 | |
| 17.0.0 | 5 / 1 | |
| 16.0.3 | 5 / 1 | |
| 16.0.2 | 5 / 1 | |
| 16.0.1 | 5 / 1 | |
| 16.0.0 | 5 / 1 | |
| 15.1.3 | 5 / 1 | |
| 15.1.2 | 5 / 1 | |
| 15.1.1 | 5 / 1 | |
| 15.1.0 | 5 / 1 | |
| 15.0.1 | 5 / 1 | |
| 15.0.0 | 6 / 3 | |
| 14.1.2 | 6 / 3 | |
| 14.1.1 | 6 / 3 | |
| 14.1.0 | 6 / 3 | |
| 14.0.1 | 6 / 3 | |
| 14.0.0 | 6 / 3 | |
| 13.6.9 | 6 / 3 | |
| 13.6.8 | 6 / 3 | |
| 13.6.7 | 6 / 3 | |
| 13.6.6 | 6 / 3 | |
| 13.6.5 | 6 / 3 | |
| 13.6.4 | 6 / 3 | |
| 13.6.3 | 6 / 3 | |
| 13.6.2 | 6 / 3 | |
| 13.6.1 | 6 / 3 | |
| 13.6.0 | 6 / 3 | |
| 13.5.2 | 6 / 3 | |
| 13.5.1 | 6 / 4 | |
| 13.5.0 | 6 / 4 | |
| 13.4.0 | 6 / 4 | |
| 13.3.0 | 6 / 4 | |
| 13.2.0 | 6 / 4 |
v20.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-08-11. This could indicate a legitimate maintainer transition or an account compromise.
v19.1.2
2 findingsThis version was published by a different npm account than previous versions on 2025-11-05. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.1.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-07-24. This could indicate a legitimate maintainer transition or an account compromise.
v19.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.1
2 findingsThis version was published by a different npm account than previous versions on 2025-11-05. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.1
2 findingsThis version was published by a different npm account than previous versions on 2025-11-05. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.