dotnet/sdk

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.

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

Scan timing: clone 25.99s · analysis 32.27s · 111.1 MB · GitHub API rate-limit (preflight)

https://github.com/dotnet/sdk · scanned 2026-06-05 22:51 UTC (4 days, 7 hours ago) · 10 languages

226 raw signals (68 security + 158 graph) 11/13 scanners ran 67th percentile · Csharp · huge (>500K LoC)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

100.0% cov · 58 findings

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`	85.0	0.20	17.00
`documentation_score`	66.0	0.15	9.90
`practices_score`	77.0	0.15	11.55
`code_quality`	80.0	0.10	8.00
Overall		1.00	81.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 0 High 12 Medium 9 Low 55 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 34 System graph 58 Crowd 0 Layer: Quality 24 Cicd 11 Software 44 Security 1 Api 1 Frontend 5 Network 1 Hardware 5

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.

Legacy markers 1 finding

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.

1 matching finding on this repo

low Old/deprecated-named symbol `applyDeltas_legacy` in src/Dotnet.Watch/Web.Middle…

View all legacy markers 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/1776470e-4bc5-4eec-a374-966bb4e999a3/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/1776470e-4bc5-4eec-a374-966bb4e999a3/

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.