Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | Gitleaks | act | dsh-session-archive |
|---|---|---|---|
| Platforms | Universal, GitHub | GitHub | DeepSeek Harness |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | MIT | MIT | Apache-2.0 |
| Stars | 30318 | 72444 | 9500 |
| Last activity | October 23, 2026 | — | September 26, 2026 |
| Install complexity | LOW | — | Easy |
| Category | Security, Git, DevOps | Testing, Git, DevOps | 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 or small team that repeatedly edits GitHub Actions workflows and wants to test a job before pushing. It provides a local run log, while a final GitHub check remains necessary. It is not suitable when exact hosted-runner parity is required. | 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. |