hhimanshu-jha/git-history-secret-scanv0.8.1Public
Git history secret scan
Finds credentials that remain reachable in local git history, not just the working tree.
Read the full description
Deleting a .env and committing does not remove its earlier reachable blob, and a hackathon repo is usually made public at submission time. Three independent stages run as parallel DAG steps (text-blob scanning across every local ref, env filenames in reachable commits, and whether a configured GitHub repository is actually public, asked of your own gh session rather than inferred from the host), then one join weighs each finding against that exposure. A stage that cannot complete becomes a labeled indeterminate rather than a silent pass, and every report states how many objects it actually walked, because a partial scan and a clean repository must not read the same. Read-only: never rewrites history or mutates the repository. The optional visibility lookup shells out to your existing gh login; when gh is missing, logged out, or bounded lookup coverage is incomplete, the report says visibility was not resolved rather than
Before you run it3 local tools
Everything here is checked on your machine when rote inspects the play. This page never learns what you have installed or which credentials you hold.
- ○python3local tool
Requires >=3.8. Run rote play inspect to check your host; unverified versions remain unknown.
- ○gitlocal tool
Must be on your PATH when used. minimum version undeclared.
- ○ghlocal tooloptional
Must be on your PATH when used. minimum version undeclared.
Inputs2, all optional
rote asks for these before running and shows the defaults it will use.
- Repo
repoAbsolute path to the repository to scan. Leave it out and the most recently committed repository found under your usual project directories is scanned instead, with the report naming which one it chose. A relative path is never right here: steps run in the play run workspace, not your shell.
optionalstringexample/Users/me/src/my-entrycustom value allowed - Budget
budgetMaximum history objects to walk. A scan that hits this limit says so in its report rather than reporting a clean result it did not earn. Raise it for a large repository.
optionalstringdefault20000example20000custom value allowed
What it changes
No write operations are declared in this version's manifest.
Credentials remain in the recipient's local rote vault; this page and the publisher never receive them.
Runtime details
- rote CLIversion 0.62.0 or newer
- Servicesnone declared
- Digest
sha256:195e5ec1018499be9bb88a8e48729094342bf60d84dd270dc914a4c51e79a124 - Archive size24955 bytes
- Published2026-09-04T14:50:41.356367+00:00
- Published withrote 0.75.0
Credential values and current readiness remain local. Opening this page never prompts for a credential, opens an authorization browser, or calls a service this play uses.
A play is a published, versioned automation package that runs on your own machine through rote, a free command-line tool. Opening this page installs nothing and runs nothing.