Setting Up Gitleaks for Secret Detection
Last updated
Last updated
Gitleaks scanning requires an additional step if you're scanning repositories belonging to an organization account. You'll need a free Gitleaks license key.
For personal account repositories, no license key is required.
Visit Gitleaks.io.
Click Sign Up to complete a Google form with your name, email, and company details.
After submitting the form, you will receive an email with your free license key.
Once you have your Gitleaks license key, it must be added as an encrypted secret in one of the following locations:
The repository
The organization
Secrets in GitHub Actions allow you to store sensitive information in your repository, organization, or specific repository environments. Ensure you follow best practices when handling and storing sensitive data, such as your Gitleaks license key.
For more information on how to use and configure secrets in GitHub Actions, visit the GitHub documentation on secrets.