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 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 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 |
v2.15.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.15.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.15.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.15.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.