yjs
Shared Editing Library
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): Postinstall only prints a sponsor message; no network/exec. Stable across versions. | ai | |
| source-diff | encoded-string-file:dist/tests.cjs | AI (source-diff): Base64 GIF test fixture in test bundle; stable false positive. | ai | |
| source-diff | encoded-string-file:dist/tests.js | AI (source-diff): Same nyan-cat test fixture in ESM test bundle; benign. | 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:dayjs | AI (typosquat): yjs is the canonical package name for the Yjs CRDT library, not a typosquat of dayjs. 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 | |
| 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 | |
| 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 |
Versions (showing 91 of 91)
| 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 | |
| 13.6.26 | 1 / 12 | |
| 13.6.25 | 1 / 12 | |
| 13.6.24 | 1 / 12 | |
| 13.6.23 | 1 / 12 | |
| 13.6.22 | 1 / 12 | |
| 13.6.21 | 1 / 12 | |
| 13.6.20 | 1 / 12 | |
| 13.6.19 | 1 / 12 | |
| 13.6.18 | 1 / 12 | |
| 13.6.17 | 1 / 12 | |
| 13.6.16 | 1 / 12 | |
| 13.6.15 | 1 / 12 | |
| 13.6.14 | 1 / 12 | |
| 13.6.13 | 1 / 12 | |
| 13.6.12 | 1 / 12 | |
| 13.6.11 | 1 / 12 | |
| 13.6.10 | 1 / 12 | |
| 13.6.9 | 1 / 12 | |
| 13.6.8 | 1 / 12 | |
| 13.6.7 | 1 / 12 | |
| 13.6.6 | 1 / 12 | |
| 13.6.5 | 1 / 12 | |
| 13.6.4 | 1 / 12 | |
| 13.6.3 | 1 / 12 | |
| 13.6.2 | 1 / 12 | |
| 13.6.1 | 1 / 12 | |
| 13.6.0 | 1 / 12 | |
| 13.5.53 | 1 / 12 | |
| 13.5.52 | 1 / 12 | |
| 13.5.51 | 1 / 12 | |
| 13.5.50 | 1 / 11 | |
| 13.5.49 | 1 / 11 | |
| 13.5.48 | 1 / 11 | |
| 13.5.47 | 1 / 11 | |
| 13.5.46 | 1 / 11 | |
| 13.5.45 | 1 / 11 | |
| 13.5.44 | 1 / 11 | |
| 13.5.43 | 1 / 11 | |
| 13.5.42 | 1 / 11 | |
| 13.5.41 | 1 / 11 | |
| 13.5.40 | 1 / 11 | |
| 13.5.39 | 1 / 11 | |
| 13.5.38 | 1 / 11 | |
| 13.5.37 | 1 / 11 | |
| 13.5.36 | 1 / 11 | |
| 13.5.35 | 1 / 11 | |
| 13.5.34 | 1 / 11 | |
| 13.5.33 | 1 / 11 | |
| 13.5.32 | 1 / 11 | |
| 13.5.31 | 1 / 11 | |
| 13.5.30 | 1 / 11 | |
| 13.5.29 | 1 / 11 | |
| 13.5.28 | 1 / 11 | |
| 13.5.27 | 1 / 11 | |
| 13.5.26 | 1 / 11 | |
| 13.5.25 | 1 / 11 | |
| 13.5.23 | 1 / 11 | |
| 13.5.22 | 1 / 11 | |
| 13.5.21 | 1 / 11 | |
| 13.5.20 | 1 / 11 | |
| 13.5.18 | 1 / 11 | |
| 13.5.16 | 1 / 11 | |
| 13.5.14 | 1 / 11 | |
| 13.5.13 | 1 / 11 | |
| 13.5.10 | 1 / 11 | |
| 13.5.9 | 1 / 11 | |
| 13.5.8 | 1 / 11 | |
| 13.5.6 | 1 / 11 | |
| 13.5.5 | 1 / 11 | |
| 13.5.4 | 1 / 11 | |
| 13.5.3 | 1 / 11 | |
| 13.5.2 | 1 / 11 | |
| 13.5.1 | 1 / 11 | |
| 13.4.13 | 1 / 11 | |
| 13.2.0 | 1 / 12 | |
| 13.1.1 | 1 / 12 | |
| 13.1.0 | 1 / 12 | |
| 13.0.8 | 1 / 12 | |
| 13.0.7 | 1 / 12 | |
| 13.0.6 | 1 / 12 | |
| 13.0.5 | 1 / 12 | |
| 13.0.4 | 1 / 12 | |
| 13.0.3 | 1 / 12 | |
| 13.0.2 | 1 / 12 | |
| 13.0.1 | 1 / 12 | |
| 13.0.0 | 1 / 12 |
v13.6.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.6.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.6.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.6.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.6.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.6.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.23
2 findingsScript: node ./sponsor-y.js
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.22
2 findingsScript: node ./sponsor-y.js
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.21
2 findingsScript: node ./sponsor-y.js
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.20
2 findingsScript: node ./sponsor-y.js
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.18
2 findingsScript: node ./sponsor-y.js
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.16
2 findingsScript: node ./sponsor-y.js
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.14
2 findingsScript: node ./sponsor-y.js
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.13
2 findingsScript: node ./sponsor-y.js
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.10
2 findingsScript: node ./sponsor-y.js
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.9
2 findingsScript: node ./sponsor-y.js
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.8
2 findingsScript: node ./sponsor-y.js
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.6
2 findingsScript: node ./sponsor-y.js
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.5
2 findingsScript: node ./sponsor-y.js
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.4
2 findingsScript: node ./sponsor-y.js
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.3
2 findingsScript: node ./sponsor-y.js
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.2
2 findingsScript: node ./sponsor-y.js
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.1
2 findingsScript: node ./sponsor-y.js
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.4.13
2 findingsScript: node ./sponsor-y.js
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.2.0
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.1
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.0
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.8
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.7
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.6
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.5
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.4
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.3
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.2
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.