@livekit/components-core
This package is a wrapper around the [livekit/client-sdk-js](https://github.com/livekit/client-sdk-js) package. It transforms the event based logic into simple to use observable state and component level APIs. This package is the core for all framework sp
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Publish-env metadata variance on trusted official package; not a risk signal. | ai | |
| provenance | no-provenance | AI (provenance): Absence of attestation alone is not a risk for this established package. | ai | |
| source-diff | net-exec-file-transition:dist/index.js | AI (source-diff): tsup build output of official WebRTC lib; network+dynamic-require is bundler/runtime wiring, not a dropper. | ai | |
| source-diff | net-exec-file-transition:dist/index.mjs | AI (source-diff): Same bundled ESM build output; benign for this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): LiveKit org team rotation; new maintainers are LiveKit employees, not external actors. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Routine team change within LiveKit org; no takeover indicators. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Established LiveKit org package; dormancy reflects release cadence, not account compromise. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Core library in a monorepo; sparse README and no keywords are expected for internal scoped packages. | ai |
Versions (showing 51 of 84)
| Version | Deps | Published |
|---|---|---|
| 0.12.14 | 3 / 11 | |
| 0.12.13 | 3 / 11 | |
| 0.12.12 | 3 / 10 | |
| 0.12.11 | 3 / 10 | |
| 0.12.10 | 3 / 10 | |
| 0.12.9 | 3 / 10 | |
| 0.12.8 | 3 / 10 | |
| 0.12.7 | 3 / 10 | |
| 0.12.6 | 3 / 10 | |
| 0.12.5 | 3 / 10 | |
| 0.12.4 | 3 / 10 | |
| 0.12.3 | 3 / 10 | |
| 0.12.2 | 3 / 10 | |
| 0.12.1 | 3 / 10 | |
| 0.12.0 | 3 / 10 | |
| 0.11.11 | 3 / 10 | |
| 0.11.10 | 3 / 10 | |
| 0.11.9 | 3 / 10 | |
| 0.11.8 | 3 / 10 | |
| 0.11.7 | 3 / 10 | |
| 0.11.6 | 3 / 10 | |
| 0.11.5 | 3 / 9 | |
| 0.11.4 | 3 / 9 | |
| 0.11.3 | 3 / 9 | |
| 0.11.2 | 3 / 9 | |
| 0.11.1 | 3 / 9 | |
| 0.11.0 | 3 / 9 | |
| 0.10.5 | 3 / 9 | |
| 0.10.4 | 3 / 9 | |
| 0.10.3 | 3 / 9 | |
| 0.10.2 | 4 / 9 | |
| 0.10.1 | 4 / 9 | |
| 0.10.0 | 4 / 9 | |
| 0.9.3 | 4 / 9 | |
| 0.9.2 | 4 / 9 | |
| 0.9.1 | 4 / 9 | |
| 0.9.0 | 4 / 9 | |
| 0.8.3 | 4 / 9 | |
| 0.8.2 | 4 / 9 | |
| 0.8.1 | 4 / 9 | |
| 0.8.0 | 4 / 9 | |
| 0.7.0 | 5 / 9 | |
| 0.6.15 | 5 / 9 | |
| 0.6.14 | 5 / 9 | |
| 0.6.13 | 5 / 9 | |
| 0.6.12 | 5 / 9 | |
| 0.6.11 | 5 / 8 | |
| 0.6.10 | 5 / 8 | |
| 0.6.9 | 5 / 8 | |
| 0.6.8 | 5 / 8 | |
| 0.6.7 | 5 / 8 |
v0.12.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: thedavidzhao.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: thedavidzhao.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: thedavidzhao.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: thedavidzhao.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: thedavidzhao.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: thedavidzhao.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: thedavidzhao.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: thedavidzhao.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: thedavidzhao.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.