Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | Gitleaks | act | restic |
|---|---|---|---|
| Platforms | Universal, GitHub | GitHub | Universal |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | MIT | MIT | BSD-2-Clause |
| Stars | 30318 | 72444 | 36796 |
| Last activity | October 23, 2026 | — | September 25, 2026 |
| Install complexity | LOW | — | متوسط: CLI ومستودع وجدولة منفصلة / Moderate: CLI, repository, and separate scheduling |
| Category | Security, Git, DevOps | Testing, Git, DevOps | Security, DevOps |
| Best use | 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. | Best for an individual developer or small team that needs encrypted, testable backups of project files and exported database dumps. It works with local or remote storage and can be scheduled by the operating system. It does not replace application-consistent database exports or recovery testing. |