@telnyx/react-native-voice-sdk
Telnyx React Native Voice SDK - A complete WebRTC voice calling solution
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:uuid-random | AI (dependencies): uuid-random is a lightweight UUID generator; appropriate for a WebRTC SDK generating call/session IDs. | ai | |
| dependencies | unvetted-dep:react-native-websocket-self-signed | AI (dependencies): Self-signed WebSocket support is expected for a React Native VoIP SDK targeting dev/enterprise SIP environments. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.4.5 | 6 / 6 | |
| 0.4.4 | 6 / 6 | |
| 0.4.3 | 6 / 6 | |
| 0.4.2 | 6 / 6 | |
| 0.4.1 | 6 / 6 | |
| 0.4.0 | 6 / 6 | |
| 0.3.0 | 6 / 6 | |
| 0.2.0 | 6 / 6 | |
| 0.1.2 | 6 / 6 | |
| 0.1.1 | 6 / 3 | |
| 0.1.0 | 6 / 3 |
v0.4.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.