High-performance code-intelligence engine for AI agents and IDE, supports 257 languages, multi repositories, based on graph, with access via CLI, MCP Server, and API. AI coding agents teammate - expose only needed information, cutting token usage up to 50x. 100% local. Discord: https://discord.gg/39MFHu3J5d
C-Rank Grade: S (Elite) - 76/100
External PR Merge Rate: 92%
Response Time: 2d
First Timer Success: 86%
zzet/gortex has a recorded first-timer success rate of 85.7%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in zzet/gortex respond to incoming external pull requests in approximately 47.6 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 75.8 places zzet/gortex in the S tier.
The external contributor pull request merge rate for zzet/gortex is 92.3%, based on public PR activity from non-core contributors.
zzet/gortex currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
High-performance code-intelligence engine for AI agents and IDE, supports 257 languages, multi repositories, based on graph, with access via CLI, MCP Server, and API. AI coding agents teammate - expose only needed information, cutting token usage up to 50x. 100% local. Discord: https://discord.gg/39MFHu3J5d
Active Go repository in zzet/gortex with ongoing community development and issue triage.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/zzet/gortex?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 14:00 UTC (14:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~31 hours (96% approval). Large PRs (>500 lines) take ~229 hours (42% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in Go.
Econumo - A personal and family budgeting app with multi-currency support, shared accounts, and flexible budgets
The Go/XGo Interpreter
sysconf and pathconf for Go, without using cgo
Is your feature request related to a problem? First — thanks for building Gortex. We evaluated 8 CodeMap tools and chose it for its cross-module contract detection on our workspace (~100 services, 20,000+ source files). It solves the "fix A breaks B" problem well. Our code agent already has grep. We installed Gortex for two reasons: Token savings: finding all consumers of an API across 80+ services takes 15-20 grep calls; Gortex reduces this to 1-2 graph queries. Blast radius awareness: get_dependents(depth=3) answers "who will this change affect?" in one call — downstream services, MQ consumers, and Controller endpoints are all surfaced. The problem: cold start takes 8-15 minutes on our workspace, making on-demand usage impractical. We only need the daemon ~10% of sessions (cross-module analysis); the other 90% it should stay stopped. With the current cold start time, developers either leave the daemon running (constant 2-3 GB memory) or skip Gortex entirely (back to grep). Desc
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to zzet/gortex, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of zzet/gortex acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 92.3% were successfully merged into the primary branch.
zzet/gortex has a recorded first-timer success rate of 85.7%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 75.8 places zzet/gortex in the Elite tier.
The external pull request merge rate is 92.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, zzet/gortex currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for zzet/gortex are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.