← Back to scan
File as GitHub Issue repo: dmonad/lib0

Push this scan report to dmonad/lib0

Click the green button below to open GitHub’s new-issue form, pre-filled with the report title, summary table, top findings, and an embedded score-card image. No authentication needed — you review on GitHub before submitting. Repobility is credited as the scanner.

Embedded score card image

This image will render at the top of the issue body. Hosted on Repobility, refreshes automatically after re-scans.

Repobility score card

Issue title

Async function without await — fire-and-forget Promise (AI mistake)

Curate findings to include

Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.

Top 5 (default)
Severity Rule Title File:line
HIGH SEC027 [SEC027] XML External Entity (XXE) — Node.js xml parsers: Node.js XML parsers can expand … src/dom.js:41
HIGH SEC083 [SEC083] JS: new RegExp() with non-literal: new RegExp(<variable>) — variable input can c… src/logging.common.js:70
HIGH SEC083 [SEC083] JS: new RegExp() with non-literal: new RegExp(<variable>) — variable input can c… src/diff/patience.js:39
HIGH SEC128 [SEC128] Async function without await — fire-and-forget Promise (AI mistake): Async call … src/delta/binding.js:42
HIGH SEC128 [SEC128] Async function without await — fire-and-forget Promise (AI mistake): Async call … src/cache.js:68
HIGH SEC128 [SEC128] Async function without await — fire-and-forget Promise (AI mistake): Async call … src/broadcastchannel.js:118
HIGH MINED115 Action `actions/setup-node` pinned to mutable ref `@v4` .github/workflows/publish.yml:57
HIGH MINED115 Action `actions/checkout` pinned to mutable ref `@v4` .github/workflows/publish.yml:56
HIGH MINED115 Action `actions/setup-node` pinned to mutable ref `@v4` .github/workflows/publish.yml:32
HIGH MINED115 Action `actions/checkout` pinned to mutable ref `@v4` .github/workflows/publish.yml:31
HIGH MINED115 Action `actions/setup-node` pinned to mutable ref `@v4` .github/workflows/publish.yml:19
HIGH MINED115 Action `actions/checkout` pinned to mutable ref `@v4` .github/workflows/publish.yml:17
HIGH MINED115 Action `denoland/setup-deno` pinned to mutable ref `@v2` .github/workflows/node.js.yml:35
HIGH MINED115 Action `actions/checkout` pinned to mutable ref `@v4` .github/workflows/node.js.yml:34
HIGH MINED115 Action `actions/setup-node` pinned to mutable ref `@v4` .github/workflows/node.js.yml:26
HIGH MINED115 Action `actions/checkout` pinned to mutable ref `@v4` .github/workflows/node.js.yml:24
HIGH MINED115 Action `actions/setup-node` pinned to mutable ref `@v4` .github/workflows/node.js.yml:13
HIGH MINED115 Action `actions/checkout` pinned to mutable ref `@v4` .github/workflows/node.js.yml:11
MED ERR002 [ERR002] Empty Catch Block: Empty catch blocks hide errors. src/storage.js:47
MED DEPCUR-GHA GitHub Action `actions/setup-node@v4` is 2 major version(s) behind (latest v6.4.0) .github/workflows/publish.yml:19
MED DEPCUR-GHA GitHub Action `actions/checkout@v4` is 2 major version(s) behind (latest v6.0.3) .github/workflows/publish.yml:17
MED DEPCUR-GHA GitHub Action `actions/setup-node@v4` is 2 major version(s) behind (latest v6.4.0) .github/workflows/node.js.yml:13
MED DEPCUR-GHA GitHub Action `actions/checkout@v4` is 2 major version(s) behind (latest v6.0.3) .github/workflows/node.js.yml:11
MED GHSA-jxxr-4gwj-5jf2 brace-expansion: GHSA-jxxr-4gwj-5jf2 package-lock.json
LOW DEPCUR-NPM npm package `dpdm` is minor version(s) behind (4.0.1 -> 4.2.0) package.json
INFO MINED044 [MINED044] Js Console Log Prod: console.log left in code. Should be replaced with logger … src/logging.node.js:79
INFO MINED044 [MINED044] Js Console Log Prod: console.log left in code. Should be replaced with logger … src/logging.js:101
INFO MINED044 [MINED044] Js Console Log Prod: console.log left in code. Should be replaced with logger … src/broadcastchannel.js:88
INFO DEPCUR-GHA GitHub Action `denoland/setup-deno@v2` is patch version(s) behind (latest v2.0.4) .github/workflows/node.js.yml:35
Reset to top 5 29 findings available (after auto-suppression of test files + won't-fix)

Issue body (markdown)

## Code-quality scan: `dmonad/lib0`

**Score: 92/100 (A-)**  ·  29 findings  ·  scanned 2026-06-05 15:25 UTC  ·  22,626 LOC

| Severity | Count |
|---|---|
| CRITICAL | 0 |
| HIGH | 18 |
| MEDIUM | 6 |
| LOW | 1 |

📊 [Full filterable report](https://repobility.com/scan/de9a206b-1305-4a6d-acd8-8c51e66dca90/)  ·  ![scorecard](https://repobility.com/scan/de9a206b-1305-4a6d-acd8-8c51e66dca90/report.png?v=1780673155-s2)

### Top findings

1. **HIGH** `SEC027` — XML External Entity (XXE) — Node.js xml parsers
   `src/dom.js:41` · A05:2021 Security Misconfiguration (XXE)
2. **HIGH** `SEC083` — JS: new RegExp() with non-literal
   `src/logging.common.js:70`
3. **HIGH** `SEC083` — JS: new RegExp() with non-literal
   `src/diff/patience.js:39`
4. **HIGH** `SEC128` — Async function without await — fire-and-forget Promise (AI mistake)
   `src/delta/binding.js:42`
5. **HIGH** `SEC128` — Async function without await — fire-and-forget Promise (AI mistake)
   `src/cache.js:68`

---

**Security note**: this issue is public. If any flagged finding is a real, exploitable vulnerability, please redirect to your `SECURITY.md` policy or open a [private security advisory](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability) instead. We're happy to close this and re-submit privately.

---

_Filed automatically. Close this issue if not useful — we won't refile. Full report: https://repobility.com/scan/de9a206b-1305-4a6d-acd8-8c51e66dca90/_
Already filed
This repo publishes a SECURITY.md policy and the scan contains 6 Critical/High security finding(s). Public issue filing would violate coordinated disclosure. Submit privately via the project's security reporting channel.
Megaproject â high spam risk
Could not determine 'dmonad/lib0' star count (GitHub API rate-limited or unreachable). When in doubt about repo size, prefer opening a focused PR or a discussion rather than an issue.
Already filed
17/31 findings (55%) on this scan are already flagged as test-file, won't-fix, or suppressed. The scan is too noisy to file as a single issue. Curate down to specific actionable findings, or address the FP source first.
I read the warnings â override Cancel

The button opens GitHubâs new-issue page in a new tab. You will see the title + body pre-filled â review, edit if you want, then click GitHubâs "Submit new issue" button. Repobility never posts anything on your behalf.

For real security findings on big repos: use the project's SECURITY.md or private advisory flow instead of a public issue.