Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | Gitleaks | goose | dsh-git-graph |
|---|---|---|---|
| Platforms | Universal, GitHub | Universal, MCP | DeepSeek Harness |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | MIT | Apache-2.0 | Apache-2.0 |
| Stars | 30318 | 55687 | 9500 |
| Last activity | October 23, 2026 | October 23, 2026 | September 25, 2026 |
| Install complexity | LOW | MEDIUM | سهل / Easy |
| Category | Security, Git, DevOps | Code Review, Multi-Agent, Workflow | Git, Workflow, UI |
| Best use | 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. | 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 a developer running several DSH sessions against one repository who wants visible branch context, history, and worktree creation in the UI. It adds session isolation and readable branch-switch guards. It may be excessive for one small change on one branch or for environments that prohibit outbound telemetry. |