(Runs locally)
Lintsure never uploads your code
Scan · ~/acme-api local
- Code uploadedNo
- Code indexedNo
- Network callsNone
- Reportlintsure-report.md
Compliance checks for the code your AI writes
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 scanClaude Code~/acme-api
Example runs. One: Lintsure scans a repo, finds a user email logged in plain text and a loan score with no human review, proposes a fix you approve, and re-checks it as Met. Two: it classifies loan scoring as high-risk under the EU AI Act and lists what's needed. Three: it lists what's left before a SOC 2 audit, in code and outside code.
A readiness tool, not an audit or legal advice. It tells you where you stand and what to fix next.
Lintsure reads your code for the questions an auditor will ask
Hover to pause. Click a question to see the framework behind it.
From one prompt to proof, in three steps
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.
Lintsure runs where your code lives and never needs a copy of it
↗
(Works where you code)
One checker, every tool you use
Connections same rules
One finding, every framework at once
Pick a finding. Lintsure shows every rule it breaks across all four frameworks, so you fix it once and close several gaps together.
EU AI ActNot affectedArt. 14 Human oversightNot affected
GDPRArt. 32 Security of processingArt. 22 Automated decisionsNot affected
SOC 2CC6.1 Logical accessNot affectedCC6.1 Logical access
ISO 27001A.8.11 Data maskingNot affectedA.8.24 Use of cryptography
Answers you can check, without uploading your code
Every answer points to a line
No vague summaries. Each answer comes with the file, the line and a status, so you can check it yourself.
How the Checker works →GapYes, in one place. api/users.ts:42 writes user.email to the logger.
GapOne live key. config/stripe.ts:4 holds a live Stripe key.
PartialMostly. api/account.ts:88 deletes the user but not their analytics events.
MetYes. admin/users.ts:51 logs every role change.
GapNot yet. api/decisions.ts:40 has no override endpoint.
No uploading, no syncing
Lintsure runs where your code already is. Pick your tool to see the one-line setup.
See all setups →What manual prep costs you today
Before an audit or a big customer's security review, someone digs through code to prove what it does. Put in your own numbers to see what that costs a year.
These are your numbers, not ours. We don't promise a saving.
Request a demoSpent on manual prep each year
$38,880
Questions
Does Lintsure upload my code?
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.
Will this make me compliant?
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.
Why not just ask Claude Code?
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.
What does it cost?
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.
Set up in a minute.
Check in one prompt.
Open source · Runs on your machine · Free
claude mcp add lintsure -- npx -y lintsure mcpnpx lintsure scanuses: lintsure/action@v1