← Home

@react-native/community-cli-plugin

Core CLI commands for React Native

51
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

react-native-botfb

Keywords

react-nativetools

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:metro AI (dependencies): metro is the official React Native bundler maintained by Meta; it is a core, expected dependency for this CLI plugin package across all versions. ai
provenance no-provenance AI (provenance): Official React Native monorepo package published by Meta's react-native-bot; repository URL anchors legitimacy. Provenance absence is common and not a risk here. ai

Versions (showing 51 of 103)

View all versions
Version Deps Published
0.86.2 7 / 1
0.86.1 7 / 1
0.86.0 7 / 1
0.85.3 7 / 1
0.85.2 7 / 1
0.85.1 7 / 1
0.85.0 7 / 1
0.84.1 7 / 1
0.84.0 7 / 1
0.83.10 7 / 1
0.83.9 7 / 1
0.83.8 7 / 1
0.83.7 7 / 1
0.83.6 7 / 1
0.83.5 7 / 1
0.83.4 7 / 1
0.83.3 7 / 1
0.83.2 7 / 1
0.83.1 7 / 1
0.83.0 7 / 1
0.82.1 7 / 1
0.82.0 7 / 1
0.81.6 7 / 1
0.81.5 7 / 1
0.81.4 7 / 1
0.81.3 7 / 1
0.81.2 7 / 1
0.81.1 7 / 1
0.81.0 7 / 1
0.80.3 8 / 1
0.80.2 8 / 1
0.80.1 8 / 1
0.80.0 8 / 1
0.79.7 8 / 1
0.79.6 8 / 1
0.79.5 8 / 1
0.79.4 8 / 1
0.79.3 8 / 1
0.79.2 8 / 1
0.79.1 8 / 1
0.79.0 8 / 1
0.78.3 10 / 1
0.78.2 10 / 1
0.78.1 10 / 1
0.78.0 10 / 1
0.77.3 10 / 1
0.77.2 10 / 1
0.77.1 10 / 1
0.77.0 10 / 1
0.76.9 11 / 1
0.76.8 11 / 1

v0.86.2

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: react-native-bot → GitHub Actions (on 2026-07-27, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (react-native-bot) on 2026-07-27, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.

v0.86.1

1 finding
INFO No provenance attestation provenance

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

v0.79.1

1 finding
INFO No provenance attestation provenance

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

v0.79.0

1 finding
INFO No provenance attestation provenance

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

v0.78.2

1 finding
INFO No provenance attestation provenance

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

v0.78.1

1 finding
INFO No provenance attestation provenance

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

v0.78.0

1 finding
INFO No provenance attestation provenance

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

v0.77.2

1 finding
INFO No provenance attestation provenance

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

v0.77.1

1 finding
INFO No provenance attestation provenance

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

v0.77.0

1 finding
INFO No provenance attestation provenance

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

v0.76.9

1 finding
INFO No provenance attestation provenance

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

v0.76.8

1 finding
INFO No provenance attestation provenance

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