Skip to content

Core concepts

GitHound connects three stages of an investigation: find matching code, keep useful evidence, and monitor new activity.

WorkflowWhat it doesWhat it keeps
SearchLooks for text in indexed snapshotsReceived matches in the current browser view
Saved searchRuns a stored query again when openedQuery text, name, and regex mode
Saved resultCaptures an individual matchReference and preview in a workspace
CollectionOrganizes evidence and scopes an investigationResults, repositories, and GitHub accounts
WatchdogEvaluates rules as incoming changes are processedMatching findings in workspace Results
Customer APIRuns supported workflows from your codeWhatever your client explicitly stores

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.

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.

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.

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.