Skip to content

One place for every compliance check your code needs

Start free with the open-source checker on your machine. When your team needs history, pull request checks and evidence for an auditor, move to the platform. Same rules, same results.

See plansRequest a demo
app.lintsure.comacme-api

Readiness by framework

EU AI Act58%

Risk tier: high-risk

GDPR81%

Controls met in code

SOC 274%

Controls met in code

ISO/IEC 2700169%

Controls met in code

Latest findings

  • Gapapi/users.ts:42Email written to logs
  • Partialml/score.py:18No human review of scores
  • Gapconfig/stripe.ts:4Live key in source

Example workspace with example data. Click the sidebar to look around.

Open source on your laptop. A platform for your team.

The checker is the same in both. The platform adds what a team and an auditor need: a shared view, a history, and proof.

Open source

Run it where you code

$ npx lintsure scan
✓ 41 controls checked
Gap      api/users.ts:42   Email written to logs
Partial  ml/score.py:18    No human review of scores
Report saved to lintsure-report.md

Free forever. Lintsure never uploads your code. Use it in Claude Code, Cursor, Codex, Windsurf, your terminal or CI.

Platform

Share it with your team

  • PR #214 Add refunds endpoint1 new gap
  • PR #213 Mask emails in loggerCloses 1 gap
  • Evidence export · SOC 2Ready

A dashboard with login, checks on every pull request, alerts, an evidence log and optional review by a real auditor. Only results sync, never your source code.

01EU AI ActAvailable →02GDPRAvailable →03SOC 2Available →04ISO/IEC 27001Available →05HIPAAPlanned →

Fits the rules you actually have

The Classifier reads your repo and suggests which frameworks apply: EU AI Act for your AI features, GDPR for EU users, SOC 2 when customers ask, HIPAA when you touch health data. You confirm the list. Lintsure checks only what applies.

Browse all frameworks →

Catch it in the pull request,
not in the audit

lintsure / check — PR #214

✕ New gap: api/refunds.ts:17 card number in logs

PCI DSS 3.4 · GDPR Art. 32 · SOC 2 CC6.1

✓ 40 controls unchanged

Suggested fix sent to the author

Evidence that writes itself

Every check is logged with the commit, the rule version and the result. Export it when your auditor asks.

The work outside code, tracked

Policies, training and vendor reviews become Officer tasks with owners and due dates, next to your code findings.

Works with your tools

An MCP server for your coding agent, a CLI for your terminal, an action for your CI. The platform reads results from all three. Open a row to copy its setup.

Claude Code
claude mcp add lintsure -- npx -y lintsure mcp
Cursor
{ "mcpServers": { "lintsure": { "command": "npx", "args": ["-y", "lintsure", "mcp"] } } }
Codex
[mcp_servers.lintsure]
command = "npx"
args = ["-y", "lintsure", "mcp"]
Windsurf
{ "mcpServers": { "lintsure": { "command": "npx", "args": ["-y", "lintsure", "mcp"] } } }
GitHub Actions
- uses: lintsure/action@v1
Terminal
npx lintsure scan

Full steps for each tool are on How it works.

Start free today. Talk to us about the platform.

The checker is open source. The team platform is in development, and a demo shows where it stands.

Set up freeRequest a demo