@livekit/protocol
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/index.d.cts | AI (source-diff): protoc-gen-es/unbuild generated build output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/index.mjs | AI (source-diff): unbuild bundled output; readable generated protobuf code. | ai | |
| source-diff | obfuscated-file:dist/index.d.mts | AI (source-diff): generated .d.ts long lines, not obfuscation. | ai | |
| provenance | publisher-changed | AI (provenance): LiveKit migrated to GitHub Actions CI publishing with SLSA attestation; this is the expected new publisher for this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by CI/CD pipeline migration; SLSA attestation confirms legitimate automated publish. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Org-wide maintainer roster update for LiveKit; consistent with legitimate team expansion. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer removals are part of the same LiveKit org restructuring; no takeover indicators. | ai |
Versions (showing 51 of 86)
| Version | Deps | Published |
|---|---|---|
| 1.50.4 | 1 / 4 | |
| 1.50.3 | 1 / 4 | |
| 1.50.2 | 1 / 4 | |
| 1.50.1 | 1 / 4 | |
| 1.50.0 | 1 / 4 | |
| 1.49.0 | 1 / 4 | |
| 1.48.2 | 1 / 4 | |
| 1.48.1 | 1 / 4 | |
| 1.48.0 | 1 / 4 | |
| 1.47.0 | 1 / 4 | |
| 1.46.8 | 1 / 4 | |
| 1.46.7 | 1 / 4 | |
| 1.46.6 | 1 / 4 | |
| 1.46.5 | 1 / 4 | |
| 1.46.4 | 1 / 4 | |
| 1.46.3 | 1 / 4 | |
| 1.46.2 | 1 / 4 | |
| 1.46.0 | 1 / 4 | |
| 1.45.8 | 1 / 4 | |
| 1.45.7 | 1 / 4 | |
| 1.45.6 | 1 / 4 | |
| 1.45.5 | 1 / 4 | |
| 1.45.4 | 1 / 4 | |
| 1.45.3 | 1 / 4 | |
| 1.45.2 | 1 / 4 | |
| 1.45.1 | 1 / 4 | |
| 1.45.0 | 1 / 4 | |
| 1.44.1 | 1 / 4 | |
| 1.44.0 | 1 / 4 | |
| 1.43.4 | 1 / 4 | |
| 1.43.2 | 1 / 4 | |
| 1.43.1 | 1 / 4 | |
| 1.43.0 | 1 / 4 | |
| 1.42.2 | 1 / 4 | |
| 1.42.1 | 1 / 4 | |
| 1.42.0 | 1 / 4 | |
| 1.41.0 | 1 / 4 | |
| 1.40.0 | 1 / 4 | |
| 1.39.3 | 1 / 4 | |
| 1.39.2 | 1 / 4 | |
| 1.39.1 | 1 / 4 | |
| 1.39.0 | 1 / 4 | |
| 1.38.0 | 1 / 4 | |
| 1.37.1 | 1 / 4 | |
| 1.37.0 | 1 / 4 | |
| 1.36.1 | 1 / 4 | |
| 1.36.0 | 1 / 4 | |
| 1.35.0 | 1 / 4 | |
| 1.34.0 | 1 / 4 | |
| 1.33.0 | 1 / 4 | |
| 1.32.1 | 1 / 4 |
v1.50.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.50.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.50.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.50.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.50.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.49.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.48.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.48.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.37.0
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (lukasio) than the most recent previously approved version (thedavidzhao) on 2025-04-21, but lukasio is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.36.1
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.36.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.35.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.33.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.1
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.