microsoft/aspire

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.

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

Scan timing: clone 20.6s · analysis 30.21s · 77.2 MB · GitHub API rate-limit (preflight)

https://github.com/microsoft/aspire · scanned 2026-06-06 00:52 UTC (4 days, 1 hour ago) · 10 languages

805 raw signals (305 security + 500 graph) 11/13 scanners ran 67th percentile · Csharp · huge (>500K LoC) System graph score 59 (higher by 27)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 1 hour ago · v2 · 307 actionable findings from 2 signal sources. 239 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 · 218 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`	100.0	0.20	20.00
`documentation_score`	67.0	0.15	10.05
`practices_score`	88.0	0.15	13.20
`code_quality`	79.0	0.10	7.90
Overall		1.00	85.9

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 40 Medium 37 Low 179 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 89 System graph 218 Crowd 0 Layer: Software 61 Quality 107 Security 9 Cicd 27 Frontend 40 Hardware 25 Api 38

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.

Duplicates & near-duplicates 3 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.

3 matching findings on this repo

low Near-duplicate function bodies in 4 places
low Near-duplicate function bodies in 3 places
low Near-duplicate function bodies in 2 places repo-level

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 `inferLegacy` in extension/src/debugger/languages/j…
low Old/deprecated-named symbol `inferLegacy` in extension/src/test/javascriptRunti…

View all legacy markers findings →

Commented-out code 18 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 (6 lines) in tests/Aspire.Hosting.CodeGeneration.TypeScrip…
info Commented-code block (5 lines) in extension/src/extension.ts:111
info Commented-code block (5 lines) in extension/src/debugger/AspireDebugSession.ts:…
info Commented-code block (7 lines) in extension/src/debugger/languages/bun.ts:47
info Commented-code block (5 lines) in extension/src/debugger/languages/dotnet.ts:213
info Commented-code block (8 lines) in extension/src/test/dashboardTelemetryRoutes.t…
info Commented-code block (5 lines) in extension/src/test/aspireTerminalProvider.tes…
info Commented-code block (5 lines) in extension/src/test/dashboardTelemetryPassthro…
info Commented-code block (8 lines) in extension/src/dcp/AspireDcpServer.ts:140
info Commented-code block (8 lines) in extension/src/dcp/DashboardTelemetryPassthrou…
info Commented-code block (13 lines) in extension/src/utils/telemetryRegistry.ts:12
info Commented-code block (6 lines) in extension/src/utils/appHostDiscovery.ts:684

View all commented-out code findings →

Config drift 19 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.

12 matching findings on this repo

low File has no detected symbols: playground/BrowserTelemetry/BrowserTelemetry.Web/…
low File has no detected symbols: playground/FoundryAgentEnterprise/frontend/vite.c…
low File has no detected symbols: playground/FoundryAgentEnterprise/frontend/eslint…
low File has no detected symbols: playground/PythonAppHost/frontend/vite.config.ts
low File has no detected symbols: playground/PythonAppHost/frontend/eslint.config.js
low File has no detected symbols: playground/TypeScriptAppHost/vite-frontend/vite.c…
low File has no detected symbols: playground/aspireify-eval/polyglot/frontend/vite.…
low File has no detected symbols: playground/aspireify-eval/dotnet-traditional/fron…
low File has no detected symbols: playground/AspireWithJavaScript/AspireJavaScript.…
low File has no detected symbols: playground/AspireWithJavaScript/AspireJavaScript.…
low File has no detected symbols: playground/AspireWithJavaScript/AspireJavaScript.…
low File has no detected symbols: playground/AspireWithJavaScript/AspireJavaScript.…

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/132ab074-fdbd-4836-8109-f7610ea43aba/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/132ab074-fdbd-4836-8109-f7610ea43aba/

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.