coprompt_Sign inRun free scan
CLIMIT open sourcenpx

Security CLI for your coding agent

Your repository scanner cannot see the key your app actually runs on. The CLI scans your live working tree — uncommitted files, .env.local, actually-installed packages.

$ npx coprompt scan
coprompt watch
$ npx coprompt watch
watching working tree · silent mode
edit lib/supabase/client.ts
■ critical service role key in client bundle
edit .env.local
◆ high SUPABASE_SERVICE_ROLE_KEY present
reported to app.coprompt.dev · nothing uploaded but findings
01

.env.local

Where your real keys live — including whether the app runs on a service role key.

02

The working tree

Code your agent generated minutes ago, before commit, where a fix is cheapest.

03

Installed packages

What is actually in node_modules, not what the lockfile claims.

Give your agent the check

~/.claude/mcp.json
{
  "mcpServers": {
    "coprompt": {
      "command": "npx",
      "args": ["coprompt", "mcp"]
    }
  }
}
Silent by default
Watch mode never interrupts your terminal. Findings go to the web app; you review them on your own schedule.

One step in CI

.github/workflows/security.yml
- name: coprompt
  run: npx coprompt scan --ci
  env:
    COPROMPT_TOKEN: ${{ secrets.COPROMPT_TOKEN }}
What leaves the machine
Findings only. Never source, never credentials. Secret values are redacted before anything is sent.