Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | D2 | act | Lychee |
|---|---|---|---|
| Platforms | Universal | GitHub | Universal |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | MPL-2.0 | MIT | MIT OR Apache-2.0 |
| Stars | 25761 | 72485 | 4065 |
| Last activity | October 11, 2026 | — | October 26, 2026 |
| Install complexity | Easy with a supported package manager; Homebrew must already be installed for this command. Official binaries, Windows, Linux, and source options are documented. | — | — |
| Category | Workflow, UI | Testing, Git, DevOps | Testing, Workflow |
| Best use | For developers and small teams that want architecture and data-flow diagrams close to the repository and reviewable as text. Use it when relationships matter more than pixel-perfect placement; not for free-form marketing design or exact manual positioning. | 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. | 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. |