← Home

@livekit/react-native

npm Repository Homepage

LiveKit for React Native

41
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

rdsathedavidzhaofeepslkmatkam_livekitraja-livekitlivekitherzoglukasiopaulwedliulkdanm_livekitocupe_livekitcacheonlysfkatbcherrylkrektdeckardjason.lernermantom.ezquerrothomasyuill-livekitlk-toubatbrianrgauslivekit

Keywords

react-nativeiosandroid

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): New maintainers have lk- prefixes consistent with LiveKit org team expansion; not a suspicious takeover. ai
maintainer-change maintainer-removed AI (maintainer-change): Removal of one maintainer alongside addition of LiveKit org members is consistent with normal team rotation. ai
phantom-deps phantom-dep:@livekit/mutex AI (phantom-deps): Same-org package; phantom-dep heuristic unreliable for indirect/conditional imports in React Native bundles. ai
publish-pattern new-deps-added AI (publish-pattern): Both added deps are established, benign polyfills; consistent with SDK evolution. ai

Versions (showing 41 of 41)

Version Deps Published
2.12.0 11 / 22
2.11.1 11 / 22
2.11.0 11 / 26
2.10.3 11 / 26
2.10.2 11 / 26
2.10.1 11 / 26
2.10.0 11 / 26
2.9.8 11 / 24
2.9.7 12 / 24
2.9.6 12 / 33
2.9.5 12 / 33
2.9.4 12 / 33
2.9.3 12 / 29
2.9.2 11 / 29
2.9.1 11 / 29
2.9.0 11 / 29
2.8.0 9 / 29
2.7.6 9 / 29
2.7.5 9 / 29
2.7.4 8 / 29
2.7.3 8 / 29
2.7.2 8 / 29
2.7.1 8 / 29
2.7.0 8 / 29
2.6.5 8 / 29
2.6.4 8 / 29
2.6.3 8 / 29
2.6.2 8 / 29
2.6.1 9 / 28
2.6.0 9 / 28
2.5.1 9 / 28
2.5.0 8 / 28
2.4.3 7 / 28
2.4.2 7 / 28
2.4.1 7 / 28
2.4.0 7 / 28
2.3.1 7 / 28
2.3.0 7 / 28
2.2.0 7 / 27
2.1.1 8 / 27
2.1.0 8 / 27

v2.12.0

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

v2.7.3

1 finding
LOW No provenance attestation provenance

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

v2.7.2

1 finding
LOW No provenance attestation provenance

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

v2.7.1

1 finding
LOW No provenance attestation provenance

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

v2.7.0

1 finding
LOW No provenance attestation provenance

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

v2.6.5

1 finding
LOW No provenance attestation provenance

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

v2.6.4

1 finding
LOW No provenance attestation provenance

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

v2.6.3

1 finding
LOW No provenance attestation provenance

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

v2.6.2

1 finding
LOW No provenance attestation provenance

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

v2.6.1

1 finding
LOW No provenance attestation provenance

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

v2.6.0

1 finding
LOW No provenance attestation provenance

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

v2.5.1

1 finding
LOW No provenance attestation provenance

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

v2.5.0

1 finding
LOW No provenance attestation provenance

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

v2.4.3

1 finding
LOW No provenance attestation provenance

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

v2.4.2

1 finding
LOW No provenance attestation provenance

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

v2.4.1

1 finding
LOW No provenance attestation provenance

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

v2.4.0

1 finding
LOW No provenance attestation provenance

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

v2.3.1

1 finding
LOW No provenance attestation provenance

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

v2.3.0

1 finding
LOW No provenance attestation provenance

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

v2.2.0

1 finding
LOW No provenance attestation provenance

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

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

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