Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | Lychee | Gitleaks | dsh-session-archive |
|---|---|---|---|
| Platforms | Universal | Universal, GitHub | DeepSeek Harness |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | MIT OR Apache-2.0 | MIT | Apache-2.0 |
| Stars | 4057 | 30430 | 9700 |
| Last activity | October 26, 2026 | October 23, 2026 | September 26, 2026 |
| Install complexity | — | LOW | Easy |
| Category | Testing, Workflow | Security, Git, DevOps | Memory, Security, Workflow |
| Best use | For documentation authors and small teams checking references locally or in CI. Start with a specific file and interpret findings; it does not establish complete site or login functionality. | 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. | 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. |