Search through troves of public data on GitHub for sensitive secrets.

How it Works

During search sessions, users will provide feedback to GitGot about search results to ignore, and GitGot prunes the set of results. Users can blacklist files by filename, repository name, username, or a fuzzy match of the file contents.

Blacklists generated from previous sessions can be saved and reused against similar queries (e.g., example.com v.s. subdomain.example.com v.s. Example Org). Sessions can also be paused and resumed at any time.

UI Commands

• Ignore similar [c]ontent: Blacklists a fuzzy hash of the file contents to ignore future results that are similar to the selected file
• Ignore [r]epo/[u]ser/[f]ilename: Ignores future results by blacklisting selected strings
• Search [/(mykeyword)]: Provides a custom regex expression with a capture group to searches on-the-fly (e.g., /(secretToken))
• [a]dd to Log: Add RegEx matches to log file, including all on-the-fly search results from search command
• Next[<Enter>], [b]ack: Advances through search results, or returns to previous results
• [s]ave state: Saves the blacklists and progress in the search results from the session
• [q]uit: Quit