SecretlyHow it works

Find leaked secrets in your GitHub repos.

Scan your own public repositories for exposed credentials. See where they appeared, get steps to fix them, and check again after cleanup.

Checking session…
Sample scan1 finding

Database connection string

In current code

config/example.env:12

Masked preview••••••••••••
How to fix

Change the exposed database password or replace the database user. Update every connection string that used it.

From detection to cleanup

  1. Scan your repository

    Choose one of your public GitHub repositories. Secretly checks the current code and commit history.

  2. Fix the exposure

    See where a potential secret was found, which kind of credential it is, and how to rotate or revoke it.

  3. Rescan after cleanup

    Check whether the secret is still detected in current code or Git history. Keep your own record of what you fixed.