Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | Gitleaks | Miller | dsh-session-archive |
|---|---|---|---|
| Platforms | Universal, GitHub | Universal, MCP, Claude Code, Codex, Cursor | DeepSeek Harness |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | MIT | BSD-2-Clause | Apache-2.0 |
| Stars | 30318 | 10050 | 9500 |
| Last activity | October 23, 2026 | October 21, 2026 | September 26, 2026 |
| Install complexity | LOW | EASY | Easy |
| Category | Security, Git, DevOps | Workflow, Data | 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. | Ideal for developers, data analysts, and operators who need to clean a CSV export, inspect JSON Lines, or summarize a large file from the terminal without starting a Python project. Use it for quick, repeatable file processing; concurrent transactions and advanced visual analysis still call for a database or complementary analytics tool. | 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. |