Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | Gitleaks | dsh-chrome | dsh-git-graph |
|---|---|---|---|
| Platforms | Universal, GitHub | DeepSeek Harness | DeepSeek Harness |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | MIT | MIT | Apache-2.0 |
| Stars | 30318 | 9 | 9500 |
| Last activity | October 23, 2026 | — | September 25, 2026 |
| Install complexity | LOW | متوسط / Moderate | سهل / Easy |
| Category | Security, Git, DevOps | Browser Automation, Security | 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 a developer debugging a local or test web UI who wants a DSH agent to see the page and network evidence in the same session. It reduces manual copying and supports interactive inspection after an explicit request. Avoid it for sensitive production accounts or if broad browser permissions are unacceptable. | 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. |