@react-native-community/cli-config-apple MIT 24 versions

@react-native-community/cli-config-apple

npm Repository Homepage

This package is part of the [React Native CLI](../../README.md). It contains utilities for building reusable commands targeting Apple platforms.

24

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

bartoszklonowskititozzzempyricalcpojermattoakesferrannpmike866krizzutrensikthymikeenicholaslee119mmazzarolorewieerjanicduplessisswaagiekelsetjohandutoitvonovakwojteg1337naturalclarconnectdotzpvinisbrentvatneevanbaconeliwhitealloycortinicosafaiyehdmitryrykunlunaleapswootwootwootreact-native-botszymonrybczakreact-native-community-botokwasniewski

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 well-established publisher (537 approved packages) within the react-native-community ecosystem; this is a legitimate maintainer transition, not a compromise.	ai	2026/04/24
publish-pattern	new-deps-added	AI (publish-pattern): picocolors replacing chalk is a standard, well-known dependency modernization. picocolors is a trusted, widely-used package with no malicious history.	ai	2026/04/23
bogus-package	bogus-package	AI (bogus-package): cpojer is a well-known Meta/React Native engineer; the spam flag is a false positive for this legitimate community CLI package. No-keywords is trivial.	ai	2026/04/23

Versions (showing 24 of 24)

Version	Deps	Published
20.1.3	4 / 2	2026-03-24
20.1.2	4 / 2	2026-02-24
20.1.1	4 / 2	2026-01-28
20.1.0	4 / 2	2026-01-07
20.0.2	4 / 2	2025-09-09
20.0.1	4 / 2	2025-08-20
20.0.0	4 / 2	2025-08-11
19.1.2	4 / 2	2025-11-05
19.1.1	4 / 2	2025-07-24
19.1.0	4 / 2	2025-07-09
19.0.0	4 / 2	2025-04-29
18.0.1	4 / 2	2025-11-05
18.0.0	4 / 2	2025-03-05
17.0.1	4 / 2	2025-11-05
17.0.0	4 / 2	2025-03-05
16.0.3	4 / 2	2025-04-17
16.0.2	4 / 2	2024-12-12
16.0.1	4 / 2	2024-12-12
16.0.0	4 / 2	2024-12-04
15.1.3	4 / 2	2024-12-12
15.1.2	4 / 2	2024-11-08
15.1.1	4 / 2	2024-11-07
15.1.0	4 / 2	2024-11-05
15.0.1	4 / 2	2024-10-31

v20.1.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v20.1.2

2 findings

HIGH Publisher changed: szymonrybczak → thymikee (on 2026-02-24) provenance

This 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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v20.1.1

2 findings

HIGH Publisher changed: szymonrybczak → thymikee (on 2026-01-28) provenance

This 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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v20.1.0

2 findings

HIGH Publisher changed: szymonrybczak → thymikee (on 2026-01-07) provenance

This 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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v20.0.2

2 findings

HIGH Publisher changed: szymonrybczak → thymikee (on 2025-09-09) provenance

This version was published by a different npm account than previous versions on 2025-09-09. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v20.0.1

2 findings

HIGH Publisher changed: szymonrybczak → thymikee (on 2025-08-20) provenance

This version was published by a different npm account than previous versions on 2025-08-20. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v20.0.0

2 findings

HIGH Publisher changed: szymonrybczak → thymikee (on 2025-08-11) provenance

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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v19.1.2

2 findings

HIGH Publisher changed: thymikee → szymonrybczak (on 2025-11-05) provenance

This 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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v19.1.1

2 findings

HIGH Publisher changed: thymikee → szymonrybczak (on 2025-07-24) provenance

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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v19.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v19.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v18.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v18.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v16.0.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v16.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v16.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v16.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v15.1.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v15.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v15.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v15.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v15.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.