microsoft/sqltoolsservice
microsoft/sqltoolsserviceClick the green button below to open GitHub’s new-issue form, pre-filled with the report title, summary table, top findings, and an embedded score-card image. No authentication needed — you review on GitHub before submitting. Repobility is credited as the scanner.
This image will render at the top of the issue body. Hosted on Repobility, refreshes automatically after re-scans.
Binary file `bin/ref/SqlScriptoria.dll` committed in source repo: `bin/ref/SqlScriptoria.d
Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.
## Code-quality scan: `microsoft/sqltoolsservice` **Score: 85/100 (A-)** · 38 findings · scanned 2026-06-05 04:15 UTC · 328,131 LOC | Severity | Count | |---|---| | CRITICAL | 0 | | HIGH | 19 | | MEDIUM | 3 | | LOW | 12 | 📊 [Full filterable report](https://repobility.com/scan/6db4f5ae-f3ca-4625-a6f1-f2bca7a92a20/) ·  ### Top findings 1. **HIGH** `SEC029` — Server-Side Request Forgery (SSRF) — outbound HTTP from user input `src/Microsoft.SqlTools.Connectors.VSCode/InternalUtilities/src/Diagnostics/Verify.cs:112` · A10:2021 SSRF 2. **HIGH** `SEC128` — Async function without await — fire-and-forget Promise (AI mistake) `src/Microsoft.SqlTools.Hosting/Hosting/Protocol/MessageWriter.cs:27` 3. **HIGH** `SEC128` — Async function without await — fire-and-forget Promise (AI mistake) `src/Microsoft.SqlTools.Authentication/Authenticator.cs:163` 4. **HIGH** `SEC128` — Async function without await — fire-and-forget Promise (AI mistake) `docs/samples/jsonrpc/netcore/executequery/Utility/SelfCleaningTempFile.cs:39` 5. **HIGH** `MINED134` — Binary file `bin/ref/SqlScriptoria.dll` committed in source repo: `bin/ref/SqlScriptoria.d `bin/ref/SqlScriptoria.dll:1` · ✓ Repobility --- **Security note**: this issue is public. If any flagged finding is a real, exploitable vulnerability, please redirect to your `SECURITY.md` policy or open a [private security advisory](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability) instead. We're happy to close this and re-submit privately. --- _Filed automatically. Close this issue if not useful — we won't refile. Full report: https://repobility.com/scan/6db4f5ae-f3ca-4625-a6f1-f2bca7a92a20/_
The button opens GitHubâs new-issue page in a new tab. You will see the title + body pre-filled â review, edit if you want, then click GitHubâs "Submit new issue" button. Repobility never posts anything on your behalf.
For real security findings on big repos: use the project's SECURITY.md or
private advisory flow instead of a public issue.