MCPcopy Index your code
hub / github.com/digininja/GitHunter

github.com/digininja/GitHunter @1.0

Chat with this repo
repository ↗ · DeepWiki ↗ · release 1.0 ↗ · + Follow
30 symbols 58 edges 3 files 2 documented · 7%
What it actually does AI analysis from the code graph — generated when you open this
loading…
README

GitHunter

Every now and then, on an internal test, you'll land on a box with a Git repository already checked out into directory. GitHunter will help you search that repository for anything juicy which could help you with other areas of your test.

GitHunter looks for: * Keywords in commit messages * Keywords in files * Interesting file names

Thanks to @michenriksen for allowing me to include his existing Gitrob signatures for doing the file name checks.

For the two keyword checks, the script uses a customisable JSON file to allow you to do either simple or regular expressesion searches, meaning you can target the discovery to your client's environment.

Installation

  1. Set up your Go environment.
  2. Checkout the project: go get https://github.com/digininja/GitHunter/
  3. Change into the project directory: cd ~/go/src/github.com/digininja/GitHunter/
  4. Get any dependencies: go get ./...

Usage

Usage is fairly simple, by default, GitHunter will look in the current directory for a .git directory and, if it finds one, will parse through it and show anything interesting it finds in either filenames or in commit comments. You can specify a different directory for the repository with the -gitdir parameter.

If you want to expand what is searched to include file contents at each commit, you can add the -grep parameter, but be warned, git, on my box at least, runs single threaded, and can take a long time to do the grepping on a large repository. It actually failed trying to grep through Metasploit, due to the sheer number of commits and content. Still worth trying it though, especially on smaller repos, as you may find something.

If you want a dump of the commit logs, without any commentary, then you can use the -dump parameter.

To specify a custom patterns file, use -patterns and to have the output without any fancy colours (easier for parsing) use -nocolours.

Testing things out

If you want a repository to test things on, have a look at my Leaky Repo which contains quite a few interesting things to find.

Extension points exported contracts — how you extend this code

CommentSignature (Interface)
(no doc) [2 implementers]
signatures.go

Core symbols most depended-on inside this repo

GetCommitString
called by 4
commit.go
GetPattern
called by 3
signatures.go
Match
called by 2
signatures.go
GetComment
called by 2
signatures.go
PrintCommit
called by 1
commit.go
AuthorDate
called by 1
commit.go
CommitDate
called by 1
commit.go
printHits
called by 1
main.go

Shape

Method 17
Function 7
Struct 5
Interface 1

Languages

Go100%

Modules by API surface

signatures.go19 symbols
main.go6 symbols
commit.go5 symbols

For agents

$ claude mcp add GitHunter \
  -- python -m otcore.mcp_server <graph>

⬇ download graph artifact