@react-native-community/cli-config-android
This package is part of the [React Native CLI](../../README.md). It contains utilities for autolinking on Android platform.
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): thymikee is a long-standing React Native community maintainer (2486 days, 1088 approved packages); transition from szymonrybczak is a legitimate team handoff within the same org. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): picocolors is a well-known, widely-trusted lightweight color library replacing chalk — a standard, safe dependency modernization pattern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): cpojer is a well-known Meta/React Native engineer, not a spam publisher. This is a stable false positive for this package. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 20.1.3 | 4 / 1 | |
| 20.1.2 | 4 / 1 | |
| 20.1.1 | 4 / 1 | |
| 20.1.0 | 4 / 1 | |
| 20.0.2 | 4 / 1 | |
| 20.0.1 | 4 / 1 | |
| 20.0.0 | 4 / 1 | |
| 19.1.2 | 4 / 1 | |
| 19.1.1 | 4 / 1 | |
| 19.1.0 | 4 / 1 | |
| 19.0.0 | 4 / 1 | |
| 18.0.1 | 4 / 1 | |
| 18.0.0 | 4 / 1 | |
| 17.0.1 | 4 / 1 | |
| 17.0.0 | 4 / 1 | |
| 16.0.3 | 4 / 1 | |
| 16.0.2 | 4 / 1 | |
| 16.0.1 | 4 / 1 | |
| 16.0.0 | 4 / 1 | |
| 15.1.3 | 4 / 1 | |
| 15.1.2 | 4 / 1 | |
| 15.1.1 | 4 / 1 |
v20.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.1.2
2 findingsThis version was published by a different npm account than previous versions on 2026-02-24. 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.
v20.1.1
2 findingsThis version was published by a different npm account than previous versions on 2026-01-28. 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.
v20.1.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-07. 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.
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
1 findingPackage 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. Only ~12% of npm packages have provenance, so this is common but not ideal.