Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | Gitleaks | dsh-git-graph | dsh-session-archive |
|---|---|---|---|
| Platforms | Universal, GitHub | DeepSeek Harness | DeepSeek Harness |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | MIT | Apache-2.0 | Apache-2.0 |
| Stars | 30318 | 9502 | 9502 |
| Last activity | October 23, 2026 | September 25, 2026 | September 26, 2026 |
| Install complexity | LOW | سهل / Easy | Easy |
| Category | Security, Git, DevOps | Git, Workflow, UI | Memory, Security, Workflow |
| 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 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. | Use it when DSH sessions pile up and you need to identify old work, archive it first, then safely remove what is no longer needed while protecting running sessions. It fits recurring cleanup and finished projects; do not enable automatic deletion before previewing the policy and checking backups. |