Privacy and security

What Lintsure reads

The files in the folder you scan, except the skipped folders (node_modules, .git, dist, build, .next, venv, .venv, __pycache__, coverage), files over 1 MB and binary files. It reads them into memory, checks them and writes a report. It doesn’t keep a copy.

What Lintsure sends

Nothing. The engine has no network code. A test in the repository fails the build if the engine’s source imports a network module or calls fetch.

Your coding agent is separate

If you use Lintsure through Claude Code, Cursor, Codex or Windsurf, the MCP server returns its report to your agent. What your agent then does with your code, including sending it to its model provider, is governed by that agent and its provider, as it already is without Lintsure.

The report can contain code locations

Reports list file paths, line numbers and rule titles, not your source code. Treat them like any other internal security document: a list of where your weak spots are.

Deterministic by design

The Checker is a fixed rule engine, not a language model. Each rule is a pure function of a line or a file. The same code gives the same report, which is what makes a report usable as evidence.

Reporting a security issue

Email support@lintsure.com with “Security” in the subject. Please don’t open a public issue for a vulnerability.