Getting Started

LintMyAI catches the mistakes AI coding assistants make -- hallucinated packages, hardcoded secrets, dead code, and more. Get running in three steps.

Step 1: Buy a License

Subscribe to LintMyAI to unlock all 28 rules. From £10/month, cancel anytime.

Subscribe to LintMyAI

Step 2: Install

Add LintMyAI to your project:

npm install -D lintmyai

Or run it directly without installing:

npx lintmyai

Step 3: Activate and Run

Activate your license (one-time per machine):

npx lintmyai activate YOUR_LICENSE_KEY

Then scan your project:

npx lintmyai

That's it. LintMyAI auto-detects your framework, loads the right rules, and reports issues in seconds.

What It Catches

LintMyAI finds the patterns AI assistants commonly get wrong:

  • Fake packages -- AI sometimes imports packages that don't exist. LintMyAI flags them before they crash your build.
  • Hardcoded secrets -- API keys and tokens left in your source code. Caught before they leak.
  • Dead code -- Functions that do nothing, error handlers that silently swallow errors, async functions that never await.
  • Security issues -- Unsafe patterns like missing input validation or exposed credentials.
  • AI quirks -- Placeholder comments, excessive hedging, over-commented code, and other AI fingerprints.

What You'll See

When you run npx lintmyai, output looks like this:

LintMyAI v1.0.0

Scanning 42 files...

src/api/auth.ts
  12:5  warning  Async function has no await expression     no-fake-async
  28:9  warning  Hardcoded secret detected: API_KEY         no-hardcoded-secrets

src/utils/helpers.ts
  5:1   warning  Package 'left-pad' may not exist on npm    no-hallucinated-packages

3 warnings found (3 rules triggered)

Each warning tells you the file, line number, what the issue is, and which rule caught it.

For CI/CD Pipelines

Set the LINTMYAI_LICENSE_KEY environment variable instead of running activate:

npx lintmyai --ci

The --ci flag exits with a non-zero code when issues are found, failing the build.

Next Steps