@liveblocks/yjs No license 64 versions

@liveblocks/yjs

npm Repository Homepage

64

Versions

—

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

nviestevenfabreliveblocks-bot

Keywords

yjsreactliveblocksreal-timetoolkitmultiplayerwebsocketscollaborationcollaborativepresencecrdtssynchronizeroomsdocumentsconflict resolution

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 is a trusted CI publisher with 9 approved packages; likely a publish environment change, not a supply chain indicator.	ai	2026/05/18
dependencies	unvetted-dep:lib0	AI (dependencies): lib0 is a core Yjs ecosystem library authored by the Yjs team; its inclusion in a Yjs integration package is expected and appropriate.	ai	2026/04/26
publish-pattern	new-deps-added	AI (publish-pattern): lib0 is the standard companion library for Yjs; adding it to @liveblocks/yjs is contextually appropriate and not a suspicious dependency addition.	ai	2026/04/26
typosquat	typosquat.levenshtein:yup	AI (typosquat): Scoped package @liveblocks/yjs cannot plausibly typosquat 'yup'; Levenshtein match is spurious for scoped namespaces.	ai	2026/04/26
typosquat	typosquat.levenshtein:dayjs	AI (typosquat): Scoped package @liveblocks/yjs cannot plausibly typosquat 'dayjs'; Levenshtein match is spurious for scoped namespaces.	ai	2026/04/26
typosquat	typosquat.levenshtein:ajv	AI (typosquat): Scoped package @liveblocks/yjs cannot plausibly typosquat 'ajv'; Levenshtein match is spurious for scoped namespaces.	ai	2026/04/26
typosquat	typosquat.levenshtein:qs	AI (typosquat): Scoped package @liveblocks/yjs cannot plausibly typosquat 'qs'; Levenshtein match is spurious for scoped namespaces.	ai	2026/04/26
typosquat	typosquat.levenshtein:rxjs	AI (typosquat): Scoped package @liveblocks/yjs cannot plausibly typosquat 'rxjs'; Levenshtein match is spurious for scoped namespaces.	ai	2026/04/26

Versions (showing 64 of 64)

Version	Deps	Published
3.19.4	6 / 0	2026-06-02
3.19.3	6 / 0	2026-05-22
3.19.2	6 / 0	2026-05-20
3.19.1	6 / 0	2026-05-13
3.19.0	6 / 0	2026-05-07
3.18.5	6 / 0	2026-04-23
3.18.4	6 / 0	2026-04-20
3.18.3	6 / 0	2026-04-17
3.18.2	5 / 3	2026-04-15
3.18.1	5 / 3	2026-04-13
3.18.0	5 / 3	2026-04-08
3.17.0	5 / 3	2026-04-02
3.16.0	5 / 3	2026-03-31
3.15.5	5 / 3	2026-03-23
3.15.4	5 / 3	2026-03-19
3.15.3	5 / 3	2026-03-17
3.15.2	5 / 3	2026-03-12
3.15.1	5 / 3	2026-03-09
3.15.0	5 / 3	2026-03-05
3.14.1	5 / 3	2026-02-26
3.14.0	5 / 3	2026-02-18
3.13.5	5 / 4	2026-02-12
3.13.4	5 / 4	2026-02-06
3.13.3	5 / 4	2026-01-22
3.13.2	5 / 4	2026-01-16
3.13.1	5 / 4	2026-01-16
3.13.0	5 / 4	2026-01-14
3.12.1	5 / 4	2025-12-19
3.12.0	5 / 4	2025-12-18
3.11.1	5 / 4	2025-12-09
3.11.0	5 / 4	2025-11-27
3.10.1	5 / 4	2025-11-13
3.10.0	5 / 4	2025-11-04
3.9.2	5 / 4	2025-10-30
3.9.1	5 / 4	2025-10-22
3.9.0	5 / 4	2025-10-16
3.8.1	5 / 4	2025-10-07
3.8.0	5 / 4	2025-09-29
3.7.1	5 / 4	2025-09-11
3.7.0	5 / 4	2025-09-11
3.6.2	5 / 4	2025-09-10
3.6.1	5 / 4	2025-09-09
3.6.0	5 / 4	2025-09-05
3.5.4	5 / 4	2025-09-05
3.5.3	5 / 4	2025-09-05
3.5.2	5 / 4	2025-09-02
3.5.1	5 / 4	2025-08-29
3.5.0	5 / 4	2025-08-28
3.4.2	5 / 4	2025-08-27
3.4.1	5 / 4	2025-08-26
3.4.0	5 / 4	2025-08-22
3.3.4	5 / 4	2025-08-14
3.3.3	5 / 4	2025-08-12
3.3.2	5 / 4	2025-08-12
3.3.1	5 / 4	2025-08-11
3.3.0	5 / 4	2025-08-08
3.2.1	5 / 4	2025-07-28
3.2.0	4 / 4	2025-07-23
3.1.4	4 / 4	2025-07-18
3.1.3	4 / 4	2025-07-15
3.1.2	4 / 4	2025-07-09
3.1.1	4 / 4	2025-07-07
3.1.0	4 / 4	2025-07-04
3.0.0	4 / 4	2025-06-17

v3.19.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.19.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.19.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.19.1

2 findings

HIGH Missing gitHead — previous versions had it provenance

This 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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.19.0

2 findings

HIGH Missing gitHead — previous versions had it provenance

This 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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.18.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.18.4

2 findings

HIGH Missing gitHead — previous versions had it provenance

This 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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.18.3

2 findings

HIGH Missing gitHead — previous versions had it provenance

This 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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.18.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.18.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.18.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.17.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.16.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.15.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.15.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.15.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.15.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.15.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.14.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.13.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.13.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.12.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.12.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.11.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.11.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.10.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.9.2

1 finding

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.9.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.8.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.8.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.7.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.7.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.6.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.6.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.6.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.5.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.5.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.5.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.5.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.4.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.4.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.3.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.3.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.3.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.3.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.