dmonad/lib0

Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.

15 of your 31 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 1.81s · analysis 6.34s · 0.9 MB · GitHub preflight 652ms

https://github.com/dmonad/lib0 · scanned 2026-06-05 15:25 UTC (5 days, 2 hours ago) · 10 languages

177 raw signals (29 security + 148 graph) 96th percentile · Javascript · medium (20-100K LoC)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 2 hours ago · v2 · 86 actionable findings from 2 signal sources. 17 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

66.7% cov · 71 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	100.0	0.15	15.00
`security_score`	98.7	0.25	24.68
`testing_score`	85.0	0.20	17.00
`documentation_score`	74.0	0.15	11.10
`practices_score`	74.0	0.15	11.10
`code_quality`	80.0	0.10	8.00
Overall		1.00	86.9

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 5 Medium 4 Low 66 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 15 System graph 71 Crowd 0 Layer: Software 50 Quality 12 Cicd 3 Api 1 Frontend 20

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Commented-out code 4 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

4 matching findings on this repo

info Commented-code block (5 lines) in src/string.js:114
info Commented-code block (6 lines) in src/prng/Xoroshiro128plus.js:50
info Commented-code block (7 lines) in src/delta/delta.test.js:1099
info Commented-code block (7 lines) in src/delta/delta.js:1138

View all commented-out code findings →

Config drift 1 finding

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

1 matching finding on this repo

high [SEC027] XML External Entity (XXE) — Node.js xml parsers: Node.js XML parsers c… src/dom.js:41

View all config drift findings →

For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.

For AI agents + API integrations

Email me when this repo regresses

Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.

API access

This page is publicly accessible at: https://repobility.com/scan/de9a206b-1305-4a6d-acd8-8c51e66dca90/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/de9a206b-1305-4a6d-acd8-8c51e66dca90/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.