Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | Lychee | act | dsh-session-archive |
|---|---|---|---|
| Platforms | 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 | 72471 | 9700 |
| Last activity | October 26, 2026 | — | September 26, 2026 |
| Install complexity | — | — | Easy |
| Category | Testing, Workflow | Testing, 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 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. |