@livekit/react-native
LiveKit for React Native
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 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 |
v2.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.10.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.10.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.9.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.