@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 |
|---|---|---|---|---|
| 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 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 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 |
v0.12.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.