Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | dsh-git-graph | Gatus | act |
|---|---|---|---|
| Platforms | DeepSeek Harness | Universal | GitHub |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | Apache-2.0 | Apache-2.0 | MIT |
| Stars | 9384 | 12381 | 72437 |
| Last activity | September 25, 2026 | September 24, 2026 | — |
| Install complexity | سهل / Easy | سهل إلى متوسط / Easy to moderate | — |
| Category | Git, Workflow, UI | Security, DevOps | Testing, Git, DevOps |
| Best use | 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. | Best for an individual developer or small team that wants self-hosted website, API, DNS, and certificate checks with a status page and threshold-based alerts. It combines active checks and simple history in one service. It does not replace resource monitoring, logs, or distributed tracing. | 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. |