google/codesearch

Fast, indexed regexp search over large file trees

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 1 hour ago
Added to GitGenius on September 17th, 2026
Created on March 30th, 2015
Open Issues & Pull Requests: 39 (+0)
GitHub issues: Enabled
Number of forks: 404
Total Stargazers: 4,011 (+0)
Total Subscribers: 117 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 648.6 days
Mean response time: 793.1 days
90th percentile: 1925.5 days
Tracked items: 12

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 4
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 929 days
Stale 30+ days: 4
Stale 90+ days: 4

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • Priority-Medium (1)
  • Type-Defect (1)
  • auto-migrated (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Code Search is a command-line tool for indexing and searching large file trees with regular expressions. It is written in Go and provides fast, indexed regexp search across source code repositories.

The tool addresses the problem of searching through large codebases efficiently. Rather than performing slow linear scans across files, Code Search builds an index of the source tree upfront, then uses that index to execute regular expression queries much faster. This indexed approach trades initial indexing time for dramatically faster subsequent searches, making it practical to search repositories that would be prohibitively slow with grep or similar line-by-line tools.

Code Search suits developers and teams working with large source trees where search performance matters. It is particularly valuable in monorepos or when performing frequent searches across substantial codebases. The tool is straightforward to install via Go's package management and operates as a set of command-line programs, making it easy to integrate into existing workflows without requiring a GUI or complex setup.

Work in the issue tracker is dominated by medium-priority defects and auto-migrated items, suggesting the tool is maintained but not undergoing active feature development or rapid iteration.