@liveblocks/core
Private internals for Liveblocks. DO NOT import directly from this package!
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Liveblocks bot publisher; gitHead absence is a publish-env artifact, not a security signal. | ai | |
| provenance | no-provenance | AI (provenance): Liveblocks publishes via a bot account without Sigstore provenance; this is a consistent pattern across their packages and not a security risk on its own. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @liveblocks/core is a scoped package in the established Liveblocks ecosystem, not a typosquat of 'cors'. The Levenshtein match is a false positive due to the 'core' substring. | ai |
Versions (showing 64 of 64)
| Version | Deps | Published |
|---|---|---|
| 3.19.4 | 0 / 0 | |
| 3.19.3 | 0 / 0 | |
| 3.19.2 | 0 / 0 | |
| 3.19.1 | 0 / 0 | |
| 3.19.0 | 0 / 0 | |
| 3.18.5 | 0 / 0 | |
| 3.18.4 | 0 / 0 | |
| 3.18.3 | 0 / 0 | |
| 3.18.2 | 0 / 8 | |
| 3.18.1 | 0 / 8 | |
| 3.18.0 | 0 / 8 | |
| 3.17.0 | 0 / 8 | |
| 3.16.0 | 0 / 8 | |
| 3.15.5 | 0 / 8 | |
| 3.15.4 | 0 / 8 | |
| 3.15.3 | 0 / 8 | |
| 3.15.2 | 0 / 8 | |
| 3.15.1 | 0 / 8 | |
| 3.15.0 | 0 / 8 | |
| 3.14.1 | 0 / 8 | |
| 3.14.0 | 0 / 9 | |
| 3.13.5 | 0 / 9 | |
| 3.13.4 | 0 / 9 | |
| 3.13.3 | 0 / 9 | |
| 3.13.2 | 0 / 9 | |
| 3.13.1 | 0 / 9 | |
| 3.13.0 | 0 / 9 | |
| 3.12.1 | 0 / 9 | |
| 3.12.0 | 0 / 9 | |
| 3.11.1 | 0 / 9 | |
| 3.11.0 | 0 / 9 | |
| 3.10.1 | 0 / 9 | |
| 3.10.0 | 0 / 9 | |
| 3.9.2 | 0 / 9 | |
| 3.9.1 | 0 / 9 | |
| 3.9.0 | 0 / 9 | |
| 3.8.1 | 0 / 9 | |
| 3.8.0 | 0 / 9 | |
| 3.7.1 | 0 / 9 | |
| 3.7.0 | 0 / 9 | |
| 3.6.2 | 0 / 9 | |
| 3.6.1 | 0 / 9 | |
| 3.6.0 | 0 / 8 | |
| 3.5.4 | 0 / 8 | |
| 3.5.3 | 0 / 8 | |
| 3.5.2 | 0 / 8 | |
| 3.5.1 | 0 / 8 | |
| 3.5.0 | 0 / 8 | |
| 3.4.2 | 0 / 8 | |
| 3.4.1 | 0 / 8 | |
| 3.4.0 | 0 / 8 | |
| 3.3.4 | 0 / 8 | |
| 3.3.3 | 0 / 8 | |
| 3.3.2 | 0 / 8 | |
| 3.3.1 | 0 / 8 | |
| 3.3.0 | 0 / 8 | |
| 3.2.1 | 0 / 8 | |
| 3.2.0 | 0 / 8 | |
| 3.1.4 | 0 / 8 | |
| 3.1.3 | 0 / 8 | |
| 3.1.2 | 0 / 8 | |
| 3.1.1 | 0 / 8 | |
| 3.1.0 | 0 / 8 | |
| 3.0.0 | 0 / 8 |
v3.19.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.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: liveblocks-bot.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.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: liveblocks-bot.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.5
2 findingsPackage name '@liveblocks/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.4
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: liveblocks-bot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.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: liveblocks-bot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.