livekit-server-sdk
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@livekit/protocol | AI (dependencies): First-party LiveKit org dependency; expected companion package for this SDK across all versions. | ai |
Versions (showing 50 of 50)
| Version | Deps | Published |
|---|---|---|
| 2.17.0 | 3 / 11 | |
| 2.16.0 | 4 / 11 | |
| 2.15.5 | 4 / 11 | |
| 2.15.4 | 4 / 11 | |
| 2.15.3 | 4 / 11 | |
| 2.15.2 | 4 / 11 | |
| 2.15.1 | 4 / 11 | |
| 2.15.0 | 4 / 11 | |
| 2.14.2 | 4 / 11 | |
| 2.14.1 | 4 / 11 | |
| 2.14.0 | 4 / 11 | |
| 2.13.3 | 4 / 11 | |
| 2.13.2 | 4 / 11 | |
| 2.13.1 | 4 / 11 | |
| 2.13.0 | 4 / 11 | |
| 2.12.0 | 4 / 11 | |
| 2.11.0 | 4 / 11 | |
| 2.10.2 | 4 / 11 | |
| 2.10.1 | 4 / 11 | |
| 2.10.0 | 4 / 11 | |
| 2.9.7 | 4 / 11 | |
| 2.9.6 | 4 / 11 | |
| 2.9.5 | 3 / 12 | |
| 2.9.4 | 3 / 12 | |
| 2.9.3 | 3 / 12 | |
| 2.9.2 | 3 / 12 | |
| 2.9.1 | 3 / 12 | |
| 2.9.0 | 3 / 12 | |
| 2.8.1 | 3 / 11 | |
| 2.8.0 | 3 / 11 | |
| 2.7.3 | 3 / 11 | |
| 2.7.2 | 3 / 11 | |
| 2.7.1 | 3 / 11 | |
| 2.7.0 | 3 / 11 | |
| 2.6.2 | 3 / 11 | |
| 2.6.1 | 3 / 11 | |
| 2.6.0 | 3 / 11 | |
| 2.5.1 | 3 / 11 | |
| 2.5.0 | 3 / 11 | |
| 2.4.0 | 3 / 16 | |
| 2.3.0 | 3 / 16 | |
| 2.2.0 | 3 / 16 | |
| 2.1.2 | 3 / 16 | |
| 2.1.1 | 3 / 16 | |
| 2.1.0 | 3 / 16 | |
| 2.0.4 | 3 / 16 | |
| 2.0.3 | 3 / 16 | |
| 2.0.2 | 3 / 16 | |
| 2.0.1 | 3 / 16 | |
| 2.0.0 | 3 / 16 |
v2.17.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.16.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
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. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.1
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. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.