microsoft/vscode-azuretools

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.

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

Scan timing: clone 1.76s · analysis 52.5s · 4.4 MB · GitHub preflight 409ms

https://github.com/microsoft/vscode-azuretools · scanned 2026-06-05 18:19 UTC (4 days, 20 hours ago) · 10 languages

268 raw signals (86 security + 182 graph) 31st percentile · Typescript · medium (20-100K LoC) System graph score 91 (lower by 27)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 20 hours ago · v2 · 131 actionable findings from 2 signal sources. 45 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 · 83 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	40.0	0.15	6.00
`security_score`	77.0	0.25	19.25
`testing_score`	56.0	0.20	11.20
`documentation_score`	65.0	0.15	9.75
`practices_score`	67.0	0.15	10.05
`code_quality`	76.6	0.10	7.66
Overall		1.00	63.9

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 10 Medium 6 Low 67 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 48 System graph 83 Crowd 0 Layer: Quality 23 Security 3 Software 78 Cicd 2 Api 1 Frontend 24

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 7 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/`.

7 matching findings on this repo

info Commented-code block (9 lines) in webview/test/theme/themeGenerator.test.ts:11
info Commented-code block (6 lines) in webview/src/webview/theme/themeGenerator.ts:59
info Commented-code block (7 lines) in webview/src/webview/theme/utils/csswg.ts:63
info Commented-code block (8 lines) in webview/src/extension/TemplateGalleryControll…
info Commented-code block (5 lines) in auth/src/providers/AzureSubscriptionProviderB…
info Commented-code block (5 lines) in utils/test/validationUtils/validationUtils.te…
info Commented-code block (5 lines) in azure/src/utils/FeedMirrorPolicy.ts:67

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

high [SEC027] XML External Entity (XXE) — Node.js xml parsers: Node.js XML parsers c… webview/src/webview/TemplateGallery/utils/renderM…:33
medium `dangerouslySetInnerHTML` used in a React component — webview/src/webview/Templ…
low Stray `console.log` in TS/JS — eng/src/esbuild/esbuildConfigs.ts:80

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/a49886d0-f961-424f-82b8-95270698730a/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/a49886d0-f961-424f-82b8-95270698730a/

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.