This document covers reporting a vulnerability in resharper-cli-mcp, the server's security model, and verifying the package you install.
Only the latest release on nuget.org receives security fixes.
Report privately through GitHub security advisories. Do not open a public issue for a security report. You can expect an acknowledgment within 7 days.
resharper-cli-mcp is a local process, and its threat model follows from that:
- It runs as a stdio subprocess launched by your MCP client, with your user privileges. It opens no network listener, makes no outbound calls, and sends no telemetry. The two tools are the whole surface; there is no plugin search or other network feature.
- Each call shells out to
jb, the ReSharper Command Line Tools you installed, which loads and analyzes your solution.jbreads and evaluates the solution's project files to do that, so inspect an untrusted solution with the same caution you would apply to opening it in an IDE. resharper_cleanupis the one tool that writes to disk: it rewrites the files you pass, in place.resharper_inspectis read-only.- Logs under
%LOCALAPPDATA%\Zphil.ReSharperCli\logscan contain absolute paths and the rule IDs and messages read from your solution. The sink keeps 31 daily rolling files, and nothing leaves the machine.
Each release ships a signed build provenance attestation covering both downloadable artifacts, the .nupkg and the .mcpb bundle Claude Desktop installs. Download either from the GitHub release and verify it as built:
gh attestation verify Zphil.ReSharperCli.<version>.nupkg --repo andypgray/resharper-cli-mcp
gh attestation verify resharper-cli-mcp-<version>.mcpb --repo andypgray/resharper-cli-mcpThe release also carries the Sigstore bundle (attestation.intoto.jsonl) for offline verification with gh attestation verify --bundle.
The nuget.org copy differs. nuget.org appends a repository signature (.signature.p7s) after upload, which changes the file hash, so the attestation matches the GitHub release copy rather than the file you download from nuget.org. Use the GitHub release asset for digest verification, and dotnet nuget verify <file> for the nuget.org repository signature.
dotnet tool install -g Zphil.ReSharperCli and, on .NET 10 or later, dnx Zphil.ReSharperCli install the same nuget.org package. resharper-cli-mcp --version prints <version>+<commit>, and that commit matches the release tag on andypgray/resharper-cli-mcp, a source cross-check that needs no tooling.
Publishing uses NuGet trusted publishing (OIDC), so there is no long-lived API key to store or leak. The release workflow builds, tests, packs, and attests every package. Builds use SourceLink and a deterministic CI configuration. Every GitHub Actions dependency is pinned to a commit SHA, every NuGet dependency is locked to a content hash in a committed packages.lock.json (restored in locked mode on CI), and the Dockerfile's base images are pinned by digest; Dependabot keeps all three current.