Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | D2 | Gitleaks | act |
|---|---|---|---|
| Platforms | Universal | Universal, GitHub | GitHub |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | MPL-2.0 | MIT | MIT |
| Stars | 25761 | 30514 | 72485 |
| Last activity | October 11, 2026 | October 23, 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. | LOW | — |
| Category | Workflow, UI | Security, Git, DevOps | Testing, Git, DevOps |
| 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 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. | 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. |