Docs / Getting started
Quickstart
Run your first Lintsure check from your terminal or your coding agent.
What you need
- Node.js 22 or newer
- A repository with JavaScript, TypeScript or Python code. Some rules also read
.env, JSON, YAML, TOML, Markdown and text files.
Run it
From your project’s folder:
npx lintsure scan
Or point it at another folder: npx lintsure scan /path/to/your-app.
You’ll see a summary, one line per finding, and a report file:
✓ 3 findings · 2 gap · 1 partial · 13 rules met · 22 outside code
partial src/billing.ts:4 Data sent over plain HTTP
gap src/config.ts:2 Secret or private key committed to source
gap src/users.ts:5 Personal data written to logs
Report saved to lintsure-report.md
The report is written to the folder you run the command from. After the findings, the CLI prints the next steps a person still needs to take and the disclaimer. Lintsure suggests; you decide.
Run it from source
The code is public at github.com/lintsure/lintsure:
git clone https://github.com/lintsure/lintsure.git
cd lintsure
npm install
npm test # builds every package and runs the test suite
node packages/cli/dist/src/index.js scan /path/to/your-app
Use it inside your coding agent
Add the MCP server, then ask your agent: check this repo for compliance. Setup for Claude Code, Cursor, Codex and Windsurf is on the MCP server page.
Next steps
- Pick the frameworks that apply to you: Configuration
- Understand what each status means: Findings and statuses
- Check every pull request: GitHub Action
Lintsure is a readiness tool, not an audit or legal advice. Results cover code only; a qualified person should review them. Disclaimer