abhigyanpatwari/GitNexus

GitNexus: The Zero-Server Code Intelligence Engine

View on GitHub ↗Jump to charts ↓Open shareable report →

abhigyanpatwari/GitNexus has 47k+ stars and 5k+ forks on GitHub, is written in TypeScript, and was last pushed on Oct 18, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 19 minutes ago
Added to GitGenius on March 2nd, 2026
Created on August 2nd, 2025
Open Issues & Pull Requests: 292 (+2)
GitHub issues: Enabled
Number of forks: 5,198
Total Stargazers: 47,934 (+2)
Total Subscribers: 166 (-1)

Repository Insights (GitGenius)

Median issue/PR response: 14.7 hours
Mean response time: 6.9 days
90th percentile: 17.8 days
Tracked items: 1,235

Maintainer activity

28 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 7% of issues opened in the past year have never received a reply. 87% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "refactor" is answered fastest, typically in about 6 hours, while "ring:3-language" waits about 4 days. 63% of tracked open issues have had no activity in three months, so the open count overstates what is actively being worked. 81% of issues opened in the past year have been closed, leaving a working backlog.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 248
New in 7 days: 17
Closed in 7 days: 17
Avg open age: 32 days
Stale 30+ days: 206
Stale 90+ days: 154

Recent activity

Opened in 7 days: 16
Closed in 7 days: 17
Comments in 7 days: 22
Events in 7 days: 26

Top labels

  • bug (295)
  • enhancement (176)
  • Language Support (126)
  • semantic-model (44)
  • rfc:scope-resolution (40)
  • ring:3-language (38)
  • refactor (32)
  • good first issue (19)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

GitNexus is a client-side code intelligence tool that builds an interactive knowledge graph of a repository and runs entirely in your browser.

The tool solves the problem of AI agents missing architectural context when analyzing code. It indexes a codebase into a knowledge graph that tracks dependencies, call chains, clusters, and execution flows, then exposes this graph through MCP tools so that AI agents like Claude Code and Cursor can understand the full structure of a project. The approach works by analyzing code relationships at scale and making that context available both through a web interface for interactive exploration and through CLI commands that integrate with AI coding assistants.

GitNexus suits developers who want their AI coding assistants to have reliable architectural awareness, particularly those using tools like Cursor, Claude Code, or other agents that benefit from deep codebase context. The web UI provides a quick way to explore any repository in the browser without setup, while the CLI with MCP integration is designed for developers who want to embed this knowledge graph into their AI agent workflows. The README positions it as deeper than DeepWiki, tracking every relationship rather than just descriptions, and emphasizes that even smaller models gain full architectural clarity when given access to the graph.

The project receives almost all of its open issues from outside users rather than the core team, indicating a substantial base of adopters reporting real-world use. Maintainers typically respond to new issues and pull requests within a day. Work in the issue tracker is dominated by bug reports, enhancement requests, and language support additions.