← Home

yjs

npm Repository Homepage

Shared Editing Library

5
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

dmonad

Keywords

YjsCRDTofflineoffline-firstshared-editingconcurrencycollaboration

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:dayjs AI (typosquat): yjs is the canonical package name for the Yjs CRDT library, not a typosquat of dayjs. Short name collision only. ai
typosquat typosquat.levenshtein:qs AI (typosquat): yjs is the canonical package name for the Yjs CRDT library, not a typosquat of qs. Short name collision only. ai
typosquat typosquat.levenshtein:rxjs AI (typosquat): yjs is the canonical package name for the Yjs CRDT library, not a typosquat of rxjs. Short name collision only. ai
typosquat typosquat.levenshtein:yup AI (typosquat): yjs is the canonical package name for the Yjs CRDT library, not a typosquat of yup. Short name collision only. ai
typosquat typosquat.levenshtein:ajv AI (typosquat): yjs is the canonical package name for the Yjs CRDT library, not a typosquat of ajv. Short name collision only. ai
bogus-package bogus-package AI (bogus-package): Inflated semver reflects real yjs versioning history; README signals are false positives for a legitimate well-known CRDT library. ai

Versions (showing 5 of 5)

Version Deps Published
13.6.31 1 / 12
13.6.30 1 / 12
13.6.29 1 / 12
13.6.28 1 / 12
13.6.27 1 / 12

v13.6.31

1 finding
LOW No provenance attestation provenance

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

v13.6.29

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.

v13.6.28

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.

v13.6.27

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.