sqltoolsservice

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.

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

Scan timing: clone 13.56s · analysis 15.52s · 51.6 MB · GitHub API rate-limit (preflight)

https://github.com/microsoft/sqltoolsservice · scanned 2026-06-05 04:15 UTC (13 hours, 21 minutes ago) · 10 languages

118 findings (38 legacy + 80 scanner) 11/13 scanners ran Scanner says 89 (lower by 9)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 13 hours, 19 minutes ago · v10 · 46 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON

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`	60.0	0.15	9.00
`practices_score`	75.0	0.15	11.25
`code_quality`	80.0	0.10	8.00
Overall		1.00	80.0

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 25 Medium 4 Low 8 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 38 9-layer 8 Crowd 0 Layer: Quality 22 Software 16 Api 1 Data 1 Frontend 1 Cicd 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.

Fragile runtime 22 findings

What it is: Code that runs but breaks under predictable input — division by zero, missing keys, unbounded loops, off-by-one slicing.

Why it matters: Reaches production undetected because happy-path tests pass. First user with a weird input crashes the request.

How AI causes it: AI loves writing the happy path; doesn't probe edge cases unless explicitly asked.

Fix approach: Add property-based tests. Wrap external inputs with explicit validators. Use the framework's typed deserializer (Pydantic, attrs).

12 matching findings on this repo

medium [SEC136] AI-typical over-broad exception handler swallowing all errors: Catch-a… src/Microsoft.SqlTools.SqlCore/SchemaCompare/Sche…:100
medium Suspicious implementation file appears unreferenced src/Microsoft.SqlTools.Credentials/Credentials/OS…:1
medium Parallel implementation file sits beside a canonical file src/Microsoft.SqlTools.Credentials/Credentials/OS…:1
low Duplicated implementation block across source files src/Microsoft.SqlTools.Hosting/Hosting/Protocol/C…:51
low [SEC132] String concat where the language has interpolation (AI style drift): S… src/Microsoft.SqlTools.ServiceLayer/AutoParameter…:37
low [SEC132] String concat where the language has interpolation (AI style drift): S… docs/samples/smo/netcore/ModifySetting/Program.cs:23
low Duplicate top-level symbol appears in a patch-style file src/Microsoft.SqlTools.Credentials/Credentials/OS…:1
low Duplicated implementation block across source files src/Microsoft.SqlTools.ServiceLayer/Agent/Jobs/Jo…:9
low Duplicated implementation block across source files src/Microsoft.SqlTools.ServiceLayer/Admin/Databas…:30
low Duplicated implementation block across source files src/Microsoft.SqlTools.ResourceProvider/ResourceP…:13
low Duplicated implementation block across source files src/Microsoft.SqlTools.ResourceProvider.DefaultIm…:2
low Duplicated implementation block across source files src/Microsoft.SqlTools.ResourceProvider.Core/Loca…:2

View all fragile runtime 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/6db4f5ae-f3ca-4625-a6f1-f2bca7a92a20/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/6db4f5ae-f3ca-4625-a6f1-f2bca7a92a20/

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.