← Home

@react-native-community/cli-tools

npm Repository Homepage
51
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.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): okwasniewski is a known React Native community contributor; addition is consistent with legitimate project growth for this well-established CLI package. ai
dependencies unvetted-dep:launch-editor AI (dependencies): launch-editor is a well-known, widely-used utility (used by webpack-dev-server, CRA) for opening files in editors. Its use here is a legitimate replacement for open+shell-quote. ai
publish-pattern new-deps-added AI (publish-pattern): The new dep (launch-editor) is a legitimate, established package replacing open+shell-quote. This is a coherent refactor, not a suspicious dependency injection. ai
provenance publisher-changed AI (provenance): thymikee is a long-standing React Native community maintainer; publisher transitions within this org are expected and legitimate. ai
phantom-deps phantom-dep:mime AI (phantom-deps): mime is declared as a runtime dependency and used in the package; phantom-dep detection is a false positive here. ai
bogus-package bogus-package AI (bogus-package): cpojer is a legitimate Meta/React Native contributor; missing description/keywords are typical for monorepo sub-packages in this project. ai
npm-metadata no-description AI (npm-metadata): Monorepo sub-package; missing description is a metadata style choice, not a malice indicator for this established package. ai

Versions (showing 51 of 118)

View all versions
Version Deps Published
20.1.3 10 / 5
20.1.2 10 / 5
20.1.1 10 / 5
20.1.0 10 / 5
20.0.2 10 / 5
20.0.1 10 / 5
20.0.0 10 / 5
19.1.2 10 / 5
19.1.1 10 / 5
19.1.0 10 / 5
19.0.0 10 / 5
18.0.1 10 / 5
18.0.0 10 / 5
17.0.1 10 / 5
17.0.0 10 / 5
16.0.3 11 / 5
16.0.2 11 / 5
16.0.1 11 / 5
16.0.0 11 / 5
15.1.3 11 / 5
15.1.2 11 / 5
15.1.1 11 / 5
15.1.0 11 / 5
15.0.1 11 / 5
15.0.0 11 / 6
14.1.2 10 / 5
14.1.1 10 / 5
14.1.0 10 / 5
14.0.1 10 / 5
14.0.0 10 / 5
13.6.9 11 / 6
13.6.8 11 / 6
13.6.7 11 / 6
13.6.6 11 / 6
13.6.5 11 / 6
13.6.4 11 / 6
13.6.3 11 / 6
13.6.2 11 / 6
13.6.1 11 / 6
13.6.0 11 / 6
13.5.2 10 / 6
13.5.1 10 / 6
13.5.0 10 / 6
13.4.0 10 / 6
13.3.0 10 / 6
13.2.0 10 / 6
13.1.0 10 / 6
13.0.1 10 / 6
13.0.0 10 / 6
12.3.7 10 / 6
12.3.6 10 / 6

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

1 finding
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

1 finding
LOW No provenance attestation provenance

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

v20.0.1

1 finding
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
LOW No provenance attestation provenance

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

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

[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 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
LOW No provenance attestation provenance

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

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

[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 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

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.

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. Consider requesting the maintainer enable provenance via CI/CD.

v15.0.0

1 finding
LOW No provenance attestation provenance

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

v14.1.2

1 finding
LOW No provenance attestation provenance

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

v14.1.1

1 finding
LOW No provenance attestation provenance

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

v14.1.0

1 finding
LOW No provenance attestation provenance

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

v14.0.1

1 finding
LOW No provenance attestation provenance

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

v14.0.0

1 finding
LOW No provenance attestation provenance

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

v13.6.9

1 finding
LOW No provenance attestation provenance

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

v13.6.8

1 finding
LOW No provenance attestation provenance

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

v13.6.7

1 finding
LOW No provenance attestation provenance

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

v13.6.6

1 finding
LOW No provenance attestation provenance

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

v12.3.7

1 finding
LOW No provenance attestation provenance

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