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
198 of your 312 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.
Upstream (GitHub) caused delay on this scan — not Repobility.
  • GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
  • Clone from GitHub took 133.97s for a 675.1 MB repo slow.
  • Repobility's analysis ran in 113.26s after the clone landed.

dotnet/runtime

https://github.com/dotnet/runtime · scanned 2026-06-05 19:50 UTC (4 days, 15 hours ago) · 10 languages

859 raw signals (293 security + 566 graph) 11/13 scanners ran 50th percentile · Csharp · huge (>500K LoC) System graph score 76 (higher by 3)

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

Complete repo analysis

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

JSON
Combined
78.6
/100
Security checks
81
84 findings
System graph
76
100.0% cov · 242 findings
Critical
1
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 65.0 0.15 9.75
security_score 100.0 0.25 25.00
testing_score 80.0 0.20 16.00
documentation_score 96.0 0.15 14.40
practices_score 77.0 0.15 11.55
code_quality 25.0 0.10 2.50
Overall 1.00 79.2
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 1 High 42 Medium 65 Low 134 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 84 System graph 242 Crowd 0 Layer: Quality 109 Cicd 21 Security 5 Software 105 Api 1 Frontend 46 Network 28 Hardware 11

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 5 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.
5 matching findings on this repo
  • low Near-duplicate function bodies in 4 places repo-level
  • low Near-duplicate function bodies in 2 places repo-level
  • low Near-duplicate function bodies in 8 places
  • low Near-duplicate function bodies in 11 places
  • low Near-duplicate function bodies in 3 places
View all duplicates & near-duplicates findings →
Commented-out code 30 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 .github/skills/ci-pipeline-monitor/scripts/va…
  • info Commented-code block (5 lines) in src/mono/browser/runtime/jiterpreter-trace-ge…
  • info Commented-code block (5 lines) in src/mono/browser/runtime/gc-handles.ts:152
  • info Commented-code block (5 lines) in src/mono/browser/runtime/globalization-locale…
  • info Commented-code block (7 lines) in src/mono/browser/runtime/http.ts:30
  • info Commented-code block (7 lines) in src/mono/browser/runtime/profiler.ts:10
  • info Commented-code block (6 lines) in src/mono/browser/runtime/interp-pgo.ts:101
  • info Commented-code block (5 lines) in src/mono/browser/runtime/diagnostics/client-c…
  • info Commented-code block (5 lines) in src/mono/browser/runtime/diagnostics/diagnost…
  • info Commented-code block (5 lines) in src/tests/run.py:16
  • info Commented-code block (6 lines) in src/tests/Common/scripts/smarty_parser.py:22
  • info Commented-code block (7 lines) in src/tests/Common/scripts/crossgen2_comparison…
View all commented-out code findings →
Config drift 3 findings
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.
3 matching findings on this repo
  • low Stray `console.log` in TS/JS — src/tests/FunctionalTests/WebAssembly/Browser/Ru…
  • low Stray `console.log` in TS/JS — src/native/rollup.config.defines.js:24
  • high Insecure pattern 'eval_used' in src/mono/browser/runtime/rollup.config.js:284 src/mono/browser/runtime/rollup.config.js:284
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/c11c5d9d-29cd-45bc-ad93-25084caec83e/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/c11c5d9d-29cd-45bc-ad93-25084caec83e/

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.