← Home

@livekit/rtc-ffi-bindings-win32-x64-msvc

npm Repository Homepage

LiveKit RTC Node FFI bindings for internal use only

22
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 No source commit

Maintainers

rdsathedavidzhaofeepslkmatkam_livekitraja-livekitlivekitherzoglukasiopaulwedliulkdanm_livekitocupe_livekitcacheonlysfkatbcherrylkrektdeckardjason.lernermantom.ezquerrothomasyuill-livekitlk-toubatbrianrgauslivekit

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Platform-specific prebuilt native binary package; no deps/tiny payload/sparse README are all expected for this pattern. ai

Versions (showing 22 of 22)

Version Deps Published
0.12.70 0 / 0
0.12.68 0 / 0
0.12.66 0 / 0
0.12.65 0 / 0
0.12.64 0 / 0
0.12.62 0 / 0
0.12.61 0 / 0
0.12.60 0 / 0
0.12.59 0 / 0
0.12.58 0 / 0
0.12.57 0 / 0
0.12.56 0 / 0
0.12.55 0 / 0
0.12.54 0 / 0
0.12.53 0 / 0
0.12.52 0 / 0
0.12.51 0 / 0
0.12.50 0 / 0
0.12.49 0 / 0
0.12.48 0 / 0
0.12.46 0 / 0
0.12.45 0 / 0

v0.12.70

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.

v0.12.68

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.

v0.12.52

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.

v0.12.51

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.

v0.12.50

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.

v0.12.49

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

INFO Publisher changed: lukasio → GitHub Actions (on 2026-03-13, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (lukasio) on 2026-03-13, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.

v0.12.48

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

INFO Publisher changed: lukasio → GitHub Actions (on 2026-02-23, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (lukasio) on 2026-02-23, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.