← Home

@cloudflare/realtimekit-react-native

npm Homepage

Cloudflare RealtimeKit SDK for react native

8
Versions
—
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

rexscariadcruz_cfjculveysejokercf-radarcf-ci-writesegments-writethibmeuxortivecf-ci2lvalentaworengathird774jasnellterinjokescelsojsteinbergergregbrimbleasapzacyg4brymwrangler-publishercf-media-managerdash_service_accountlerwincfcf-npm-publishsimonabadoiucms1919mgirouard-cfmusa-cfvaishakpdineshichernetsky-cfjseba_cfgabivlj-cfganders-cloudflarensharma-cfmikenomitchtlefebvre_cfnafeezcfeduardo-vargasthreepointonextuc

Keywords

react-nativeiosandroid

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Cloudflare-published package; lack of provenance is common and not indicative of risk here. ai
dependencies unvetted-dep:node-libs-react-native AI (dependencies): node-libs-react-native is a standard React Native polyfill shim; expected dependency for this SDK. ai
dependencies unvetted-dep:text-encoding-polyfill AI (dependencies): text-encoding-polyfill is a standard, benign polyfill; stable false positive for this package. ai

Versions (showing 8 of 8)

Version Deps Published
1.0.0 5 / 0
0.3.2 5 / 0
0.3.0 5 / 0
0.2.1 5 / 0
0.1.2 6 / 0
0.1.1 6 / 0
0.1.0 6 / 0
0.0.1 6 / 0

v1.0.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.3.2

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.

v0.3.0

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.

v0.2.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.

v0.1.2

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.

v0.1.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.

v0.1.0

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.

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