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.
Sign up free Scan another repo
37 of your 56 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

LadybirdBrowser/ladybird

https://github.com/LadybirdBrowser/ladybird · scanned 2026-06-05 09:01 UTC (5 days, 19 hours ago) · 10 languages

1179 raw signals (51 security + 1128 graph) 11/13 scanners ran 68th percentile · C · medium (20-100K LoC) System graph score 67 (lower by 5)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Combined
73.1
/100
Security checks
79
12 findings
System graph
67
100.0% cov · 520 findings
Critical
0
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 75.0 0.15 11.25
security_score 100.0 0.25 25.00
testing_score 0.0 0.20 0.00
documentation_score 60.0 0.15 9.00
practices_score 61.0 0.15 9.15
code_quality 80.0 0.10 8.00
Overall 1.00 62.4
security_score may be inflated — optional security scanners were skipped on this fast scan
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 140 Medium 32 Low 178 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 12 System graph 520 Crowd 0 Layer: Quality 212 Security 150 Software 79 Cicd 4 Api 1 Frontend 80 Network 1 Hardware 5

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.

Duplicates & near-duplicates 6 findings
What it is: Same function copy-pasted into multiple modules with minor variations.
Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.
How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.
Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.
6 matching findings on this repo
  • low Near-duplicate function bodies in 3 places repo-level
  • low Near-duplicate function bodies in 2 places repo-level
  • low Near-duplicate function bodies in 7 places repo-level
  • low Near-duplicate function bodies in 6 places repo-level
  • low Near-duplicate function bodies in 18 places repo-level
  • low Near-duplicate function bodies in 10 places
View all duplicates & near-duplicates findings →
Legacy markers 2 findings
What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.
Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.
How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.
Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.
2 matching findings on this repo
  • low Old/deprecated-named symbol `cssSizeToLegacy` in Tests/LibWeb/Text/input/wpt-im…
  • low Old/deprecated-named symbol `cssSizeToLegacy` in Tests/LibWeb/Text/input/wpt-im…
View all legacy markers findings →
Commented-out code 124 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/`.
12 matching findings on this repo
  • info Commented-code block (5 lines) in Tests/LibWeb/Text/input/wpt-import/streams/re…
  • info Commented-code block (5 lines) in Tests/LibWeb/Text/input/wpt-import/streams/re…
  • info Commented-code block (5 lines) in Tests/LibWeb/Text/input/wpt-import/streams/re…
  • info Commented-code block (5 lines) in Tests/LibWeb/Text/input/wpt-import/streams/re…
  • info Commented-code block (6 lines) in Tests/LibWeb/Text/input/wpt-import/wasm/jsapi…
  • info Commented-code block (5 lines) in Tests/LibWeb/Text/input/wpt-import/webxr/reso…
  • info Commented-code block (20 lines) in Tests/LibWeb/Text/input/wpt-import/intersect…
  • info Commented-code block (8 lines) in Tests/LibWeb/Text/input/wpt-import/html/seman…
  • info Commented-code block (5 lines) in Tests/LibWeb/Text/input/wpt-import/html/resou…
  • info Commented-code block (5 lines) in Tests/LibWeb/Text/input/wpt-import/html/infra…
  • info Commented-code block (6 lines) in Tests/LibWeb/Text/input/wpt-import/html/webap…
  • info Commented-code block (5 lines) in Tests/LibWeb/Text/input/wpt-import/html/webap…
View all commented-out code 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/ade0aeb2-8611-4ef2-a50d-31b9bd439477/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/ade0aeb2-8611-4ef2-a50d-31b9bd439477/

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.