← Home

@lexical/yjs

npm Repository Homepage
23
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

fantactukazurfyxacywatsonipavlov001trueadmetrepum

Keywords

reactlexicaleditorrich-textcolllaborationyjscrdt

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/LexicalYjs.prod.js AI (source-diff): Standard minified production bundle for this Meta/Facebook package. ai
source-diff obfuscated-file:dist/LexicalYjs.prod.mjs AI (source-diff): Standard minified production ESM bundle for this Meta/Facebook package. ai
provenance missing-githead AI (provenance): Well-established Facebook/Lexical monorepo package; missing gitHead likely reflects a CI/CD environment change, not a supply chain compromise. No other risk signals present. ai
provenance no-provenance AI (provenance): Established Facebook/Meta Lexical package; lack of Sigstore provenance is a process gap, not a security indicator for this well-known package. ai
typosquat typosquat.levenshtein:ajv AI (typosquat): @lexical/yjs is a legitimate Facebook/Meta Lexical editor package; Levenshtein match to ajv is a false positive for this scoped package. ai
typosquat typosquat.levenshtein:dayjs AI (typosquat): @lexical/yjs is a legitimate Facebook/Meta Lexical editor package; Levenshtein match to dayjs is a false positive for this scoped package. ai
dependencies unvetted-dep:@lexical/selection AI (dependencies): @lexical/selection is a sibling package in the same Facebook/Meta Lexical monorepo, pinned to the same version. Expected internal dependency. ai
dependencies unvetted-dep:@lexical/offset AI (dependencies): @lexical/offset is a sibling package in the same Facebook/Meta Lexical monorepo, pinned to the same version. Expected internal dependency. ai
typosquat typosquat.levenshtein:qs AI (typosquat): @lexical/yjs is a legitimate Facebook/Meta Lexical editor package; Levenshtein match to qs is a false positive for this scoped package. ai
typosquat typosquat.levenshtein:rxjs AI (typosquat): @lexical/yjs is a legitimate Facebook/Meta Lexical editor package; Levenshtein match to rxjs is a false positive for this scoped package. ai
typosquat typosquat.levenshtein:yup AI (typosquat): @lexical/yjs is a legitimate Facebook/Meta Lexical editor package; Levenshtein match to yup is a false positive for this scoped package. ai

Versions (showing 23 of 23)

Version Deps Published
0.45.0 3 / 1
0.44.0 2 / 0
0.43.0 3 / 0
0.42.0 3 / 0
0.41.0 3 / 0
0.40.0 3 / 0
0.39.0 3 / 0
0.38.2 3 / 0
0.38.1 3 / 0
0.38.0 3 / 0
0.37.0 3 / 0
0.36.2 3 / 0
0.36.1 3 / 0
0.36.0 3 / 0
0.35.0 3 / 0
0.34.0 3 / 0
0.33.1 3 / 0
0.33.0 3 / 0
0.32.1 3 / 0
0.32.0 3 / 0
0.31.2 3 / 0
0.31.1 3 / 0
0.31.0 3 / 0

v0.45.0

3 findings
HIGH New obfuscated file: dist/LexicalYjs.prod.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/LexicalYjs.prod.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

INFO No provenance attestation provenance

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

v0.43.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.

v0.42.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: zurfyx.

LOW No provenance attestation provenance

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

v0.41.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: zurfyx.

LOW No provenance attestation provenance

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

v0.40.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: zurfyx.

LOW No provenance attestation provenance

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

v0.38.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.

v0.38.1

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.

v0.38.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.

v0.37.0

1 finding
INFO No provenance attestation provenance

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

v0.36.2

1 finding
INFO No provenance attestation provenance

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

v0.36.1

1 finding
INFO No provenance attestation provenance

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

v0.36.0

1 finding
INFO No provenance attestation provenance

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

v0.35.0

1 finding
INFO No provenance attestation provenance

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

v0.34.0

1 finding
INFO No provenance attestation provenance

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

v0.33.1

1 finding
INFO No provenance attestation provenance

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

v0.33.0

1 finding
INFO No provenance attestation provenance

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

v0.32.1

1 finding
INFO No provenance attestation provenance

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

v0.32.0

1 finding
INFO No provenance attestation provenance

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

v0.31.2

1 finding
INFO No provenance attestation provenance

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

v0.31.1

1 finding
INFO No provenance attestation provenance

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

v0.31.0

1 finding
INFO No provenance attestation provenance

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