(Runs locally)
Lintsure never uploads your code
Scan · ~/acme-api local
- Code uploadedNo
- Code indexedNo
- Network callsNone
- Reportlintsure-report.md
Lintsure works out which compliance standards apply to you, then checks your code against them. Every finding shows the file and line, the rules it breaks, and a fix.
npx lintsure scanExample runs. One: Lintsure scans a repo and finds a user email in the logs, a committed secret key and a loan score with no human review. Two: it proposes a one-line fix, you approve it, and the re-check marks it Met. Three: it explains that loan scoring is high-risk under the EU AI Act from 2 December 2027. Four: it lists what's left before a SOC 2 audit.
A readiness tool, not an audit or legal advice. It tells you where you stand and what to fix next.
Hover to pause. Click a question to see the framework behind it.
You ask your coding agent. Lintsure finds where personal data goes, checks each rule the same way every time, and hands back fixes for you to approve.
(Runs locally)
Scan · ~/acme-api local
(Works where you code)
Connections same rules
Pick a finding. Lintsure shows every rule it breaks across all four frameworks, so you fix it once and close several gaps together.
Plain guides for software teams, and a page for each of the 47 checks with an example and a fix.
Every release is public, with the commits behind it. Here's what changed lately.
v0.3.0 · 9 Nov 2026
OWASP Top 10:2025A fifth framework in Beta: all ten OWASP Top 10:2025 categories, described in our own words, with 31 new rules and eleven existing rules mapped to them.
v0.2.0 · 8 Nov 2026
Reports you can act on, rules you can measureLintsure now remembers what your team already knows: a baseline shows what is new, fixed or unchanged, and accepted findings carry a reason and a name. Every rule is scored against a labelled test set.
v0.1.3 · 8 Nov 2026
Ask first, every timeA hard rule for every agent that uses Lintsure: explain what it plans to do, point to the exact line, say why and what you gain, then wait for a clear yes.
If you run Lintsure in your company, send a review
Good or bad, we read every one. We only publish it if you say we can.
No. It runs on your machine or in your own CI and never sends your code to us. Your coding agent, if you use one, follows its own provider's rules.
No tool can do that alone. Lintsure is a readiness tool, not an audit or legal advice. It shows what your code proves, what it doesn't, and what lives outside code, like policies and training.
A general agent will give a different answer each time, and it may say a control is met when it isn't. Lintsure's Checker is a fixed rule engine: same input, same result. Only it can mark a control as Met.
The checker is free and open source. Lintsure Monitor, a paid service with checks on every pull request and review by a real auditor, is coming later. Request a demo to see it.
Open source · Runs on your machine · Free
claude mcp add lintsure -- npx -y @lintsure/mcpnpx lintsure scanuses: lintsure/action@v1Your privacy choices
We use one storage item to remember this choice. With your OK, we'd also count visits to see which pages help. No ads, no selling data. Privacy notice
Strictly necessary
Remembers your privacy choice. Always on.