Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | Lychee | goose | Gitleaks |
|---|---|---|---|
| Platforms | Universal | Universal, MCP | Universal, GitHub |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | MIT OR Apache-2.0 | Apache-2.0 | MIT |
| Stars | 4057 | 55847 | 30430 |
| Last activity | October 26, 2026 | October 23, 2026 | October 23, 2026 |
| Install complexity | — | MEDIUM | LOW |
| Category | Testing, Workflow | Code Review, Multi-Agent, Workflow | Security, Git, DevOps |
| Best use | For documentation authors and small teams checking references locally or in CI. Start with a specific file and interpret findings; it does not establish complete site or login functionality. | Best for an individual developer or small team that wants an AI agent to complete an inspectable task in a working copy: understand files, make a bounded change, and run a test. Start with manual approval and scope the folder and tools. Do not give it broad access to production or sensitive data. | Best for an individual developer or small team that wants a local pre-commit secret scan plus a second CI gate. It is especially useful around deployment configuration and environment files. It does not replace a secret manager or credential revocation after a leak. |