Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | zoxide | Gitleaks | act |
|---|---|---|---|
| Platforms | Universal | Universal, GitHub | GitHub |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | MIT | MIT | MIT |
| Stars | 40336 | 30430 | 72471 |
| Last activity | October 24, 2026 | October 23, 2026 | — |
| Install complexity | — | LOW | — |
| Category | Workflow | Security, Git, DevOps | Testing, Git, DevOps |
| Best use | For developers switching among many directories in an interactive terminal. It learns from visited paths and helps you return; use explicit paths for scripts and deployments that require a fixed destination. | 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. |