SSMS Claude Chat security report
SSMS Claude Chat is checked by more than a dozen well-known security tools every time the code changes, and again every day, because new problems are discovered all the time. This page shows the latest results, updated automatically after each scan.
Scanned code version 00a2bcd (release v1.4.23) on 27 October 2026 at 04:11 UTC.
| Check | What it looks for | Result | Findings |
|---|---|---|---|
| Code analysis GitHub CodeQL |
Reads the source code looking for security bugs such as injection or unsafe data handling. | ✓ Passed | None |
| Security rules Semgrep, Microsoft DevSkim |
Checks the code against thousands of known insecure patterns. | ✓ Passed | 1 medium 2 low |
| Leaked passwords and keys Gitleaks, TruffleHog |
Searches the whole history of the code for passwords, keys or tokens left in by mistake. | ✓ Passed | None |
| Vulnerable libraries OSV-Scanner, Trivy |
Compares every library used with public vulnerability databases. Includes libraries used only while building, which are not part of the installer. What ships is checked by the installer scan below. |
✓ Passed | 5 high 9 medium |
| Installer scan ClamAV, Grype, Syft |
Scans the finished installer for viruses and for vulnerable components, and lists everything inside it. | ✓ Passed | None |
| Build pipeline safety actionlint, zizmor |
Checks that the automated build cannot be tampered with or leak its credentials. | ✓ Passed | None |
| Build script checks PSScriptAnalyzer |
Checks the build scripts for unsafe or error-prone code. | ✓ Passed | None |
| Security best practices OpenSSF Scorecard |
Grades how the project is run: reviews, pinned dependencies, token permissions and more. | Not run | – |
Signed installer: not yet. Code signing is being set up; until then Windows may show a “Windows protected your PC” message when you run the setup.
What the results mean
- Passed means the check found nothing at or above the level we treat as unacceptable. Smaller findings are still counted and reviewed.
- Findings are counted, but the details are not published here. That way nobody can learn about a problem before it is fixed.
- Vulnerable libraries also counts libraries that are only used to build SSMS Claude Chat and are not inside the installer. The Installer scan checks exactly what you download.
What’s inside the installer
The installer scan also produces a full list of what’s inside the download (a “software bill of materials”): sbom.spdx.json.
How SSMS Claude Chat keeps you safe
- Nothing changes in your database without your OK. You see the exact SQL and where it will run, then click Yes or No. You can also switch changes off completely.
- Looking is read-only. When Claude reads data to answer a question, it can’t write, and every query is undone afterwards.
- Your Claude password is never seen. You sign in to Claude in your browser.
- Your data stays on your computer, apart from what is sent to Claude to answer you. See the FAQ.
- Claude can only do what your SQL Server login allows.
Found a security problem?
Please tell us privately rather than in a public issue: see how to report a vulnerability.