@livekit/rtc-node
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): NAPI-RS musl detection pattern; stable and benign for this native binding package. | ai | |
| semgrep | semgrep:child-process-execsync | AI (semgrep): execSync('which ldd') is a documented NAPI-RS musl detection idiom; not a risk for this package. | ai | |
| dependencies | unvetted-dep:@livekit/typed-emitter | AI (dependencies): First-party LiveKit org dependency; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@livekit/rtc-ffi-bindings | AI (dependencies): First-party LiveKit FFI bindings; stable dependency pattern for this SDK package. | ai | |
| phantom-deps | phantom-dep:pino-pretty | AI (phantom-deps): pino-pretty is a declared runtime dep used as a pino transport; not directly imported in source but legitimately present. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.13.29 | 6 / 7 | |
| 0.13.28 | 6 / 7 | |
| 0.13.27 | 6 / 7 | |
| 0.13.26 | 6 / 7 | |
| 0.13.25 | 6 / 7 | |
| 0.13.14 | 5 / 6 | |
| 0.13.13 | 5 / 6 | |
| 0.13.12 | 5 / 6 |
v0.13.29
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.28
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.26
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.25
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.