Core concepts
GitHound connects three stages of an investigation: find matching code, keep useful evidence, and monitor new activity.
Choose the right workflow
Section titled “Choose the right workflow”| Workflow | What it does | What it keeps |
|---|---|---|
| Search | Looks for text in indexed snapshots | Received matches in the current browser view |
| Saved search | Runs a stored query again when opened | Query text, name, and regex mode |
| Saved result | Captures an individual match | Reference and preview in a workspace |
| Collection | Organizes evidence and scopes an investigation | Results, repositories, and GitHub accounts |
| Watchdog | Evaluates rules as incoming changes are processed | Matching findings in workspace Results |
| Customer API | Runs supported workflows from your code | Whatever your client explicitly stores |
Workspaces
Section titled “Workspaces”A workspace groups your queries, captured matches, monitors, and results. Check the active workspace before saving evidence or creating a monitor. Account usage limits span workspaces; creating another workspace does not add search allowance.
Indexed snapshots
Section titled “Indexed snapshots”Search examines indexed versions of public GitHub files. The commit reference identifies the snapshot associated with a result. A repository may since have changed, moved, or become unavailable.
A result preview is an excerpt. Saving it does not archive the complete file or repository. No matches means no matching code was returned from the searched index, not proof of absence across GitHub.
Received matches and completeness
Section titled “Received matches and completeness”Matches arrive incrementally. Filters, sorting, and table exports operate on matches received by the browser. Stopped, interrupted, or limited searches do not constitute an exhaustive result set. Preserve completion status when you record an investigation.
Matches and conclusions
Section titled “Matches and conclusions”A text match is evidence to inspect. Relevance scores help order review; they do not establish credential validity or malicious intent. Review the repository, path, surrounding code, and commit before acting.