Skip to content
Back to search

gitnexus-marketplace

MarketplaceWorks with Claude CodeGitHub

GitNexus: The Zero-Server Code Intelligence Engine

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/abhigyanpatwari/GitNexus with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/abhigyanpatwari/GitNexus'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/abhigyanpatwari-gitnexus/badge.svg)](/listings/abhigyanpatwari-gitnexus)

HTML

<a href="/listings/abhigyanpatwari-gitnexus"><img src="/api/listings/abhigyanpatwari-gitnexus/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

# 1. Index your repo (run from repo root)
npx gitnexus analyze

# 2. Connect your editors (one-time, auto-detects Claude Code, Cursor, Codex, …)
npx gitnexus setup

That's it. `analyze` indexes the codebase, installs agent skills, registers Claude Code hooks, and creates `AGENTS.md` / `CLAUDE.md` context files — all in one command. `setup` writes the MCP config so your AI agent can use the graph.

<details> <summary><strong>Install problems?</strong> npm 11 crash · slow cold install · no C++ toolchain</summary>

> **On npm 11.x?** `npx` can crash during install with `Cannot destructure property 'package' of 'node.target'` (an npm/arborist bug, before GitNexus runs). Use pnpm instead — it builds the native deps explicitly: > > ```bash > pnpm --allow-build=@ladybugdb/core --allow-build=gitnexus --allow-build=tree-sitter dlx gitnexus@latest analyze > ``` > > Or install globally (`npm install -g gitnexus@latest`) and run `gitnexus analyze`. See [#1939](https://github.com/abhigyanpatwari/GitNexus/issues/1939).

> **Fastest MCP startup:** install globally (`npm i -g gitnexus`) before running `gitnexus setup` — this writes an absolute-path MCP config that bypasses `npx` entirely. On a cold cache, an `npx`-based MCP install can exceed Claude Code's `MCP_TIMEOUT` default (~30s).

> **No C++ toolchain?** Set `GITNEXUS_SKIP_OPTIONAL_GRAMMARS=1` before `npm install -g gitnexus` to skip the vendored grammar materialize/build for `tree-sitter-dart`, `tree-sitter-proto`, `tree-sitter-swift`, and `tree-sitter-kotlin` — those four languages won't be parsed, but install completes in seconds without `python3`/`make`/`g++`. Strict `=1` only — any other value falls through to the rebuild.

> **Local embeddings are opt-in.** Default `npm install` does not fetch `@huggingface/transformers` or `onnxruntime-node`. Run `gitnexus embeddings install` (or `gitnexus analyze --embeddings`, which auto-heals) to fetch the stack through your npm registry config into `~/.gitnexus/embedding-runtime`. CUDA GPU binaries still use NuGet via `--cuda` ([#2370](https://github.com/abhigyanpatwari/GitNexus/issues/2370)). The prefix needs Node with `module.registerHooks` (≥ 22.15 on 22.x, ≥ 23.5 on 23.x). A leftover 1.6.12 package-first tree is residual until a clean reinstall; `--force` only refreshes prefix overrides.

> **About `tree-sitter-kotlin`:** like Dart/Proto/Swift, Kotlin is a **vendored** grammar (under `gitnexus/vendor/tree-sitter-kotlin`). Upstream ships **source only** (no prebuilt binaries), so GitNexus cross-builds the platform prebuilds itself (via the `build-tree-sitter-prebuilds` GitHub Actions workflow) and vendors them — the same uniform pipeline used for Dart, Proto, and Swift. `node-gyp-build` selects the right `.node` at require time, so **no C/C++ toolchain is needed**. If no prebuild matches your platform-arch, only Kotlin (`.kt`/`.kts`) parsing is unavailable; the rest of `gitnexus` is unaffected.

</details>

Deploy to Render

Deploy GitNexus in one click:

The Blueprint creates two services. `gitnexus-server` runs `gitnexus serve` as a private service: no public URL, reachable only over Render's private network, with a persistent disk for indexes and cloned repos. `gitnexus-web` is the public one. It serves the UI and reverse-proxies `/api/*` to the server, so the browser talks to a single origin.

At the Blueprint's defaults this runs about **$35/month**: $25 for the server's `standard` instance, $7 for the web service's `starter` instance, and $2.50 for the 10 GB disk. See [Render's pricing](https://render.com/pricing) for other plans.

The deploy generates an access token, and the UI asks for it on first use:

1. Open the `gitnexus-web` service in your [Render dashboard](https://dashboard.render.com/). 2. Copy `GITNEXUS_SERVE_AUTH_TOKEN` from its **Environment** tab. 3. Load the site and paste the token into the prompt (or the settings panel).

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 19 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. {
  2. "name": "gitnexus-marketplace",
  3. "owner": {
  4. "name": "GitNexus",
  5. "email": "nico@gitnexus.dev"
  6. },
  7. "metadata": {
  8. "description": "Code intelligence powered by a knowledge graph — execution flows, blast radius, and semantic search",
  9. "homepage": "https://github.com/nicosxt/gitnexus"
  10. },
  11. "plugins": [
  12. {
  13. "name": "gitnexus",
  14. "version": "1.6.12",
  15. "source": "./gitnexus-claude-plugin",
  16. "description": "Code intelligence powered by a knowledge graph. Provides execution flow tracing, blast radius analysis, and augmented search across your codebase."
  17. }
  18. ]
  19. }
README.md · README · 193 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. # GitNexus
  2. <div align="center">
  3. <a href="https://trendshift.io/repositories/19809" target="_blank">
  4. <img src="https://trendshift.io/api/badge/repositories/19809" alt="abhigyanpatwari%2FGitNexus | Trendshift" style="width: 250px; height: 55px;" width="250" height="55"/>
  5. </a>
  6. <p>
  7. <a href="https://discord.gg/MgJrmsqr62">
  8. <img src="https://img.shields.io/discord/1477255801545429032?color=5865F2&logo=discord&logoColor=white" alt="Discord"/>
  9. </a>
  10. <a href="https://www.npmjs.com/package/gitnexus">
  11. <img src="https://img.shields.io/npm/v/gitnexus.svg" alt="npm version"/>
  12. </a>
  13. <a href="https://polyformproject.org/licenses/noncommercial/1.0.0/">
  14. <img src="https://img.shields.io/badge/License-PolyForm%20Noncommercial-blue.svg" alt="License: PolyForm Noncommercial"/>
  15. </a>
  16. <a href="https://securityscorecards.dev/viewer/?uri=github.com/abhigyanpatwari/GitNexus">
  17. <img src="https://api.securityscorecards.dev/projects/github.com/abhigyanpatwari/GitNexus/badge" alt="OpenSSF Scorecard"/>
  18. </a>
  19. <a href="https://github.com/abhigyanpatwari/GitNexus/actions/workflows/ci.yml">
  20. <img src="https://github.com/abhigyanpatwari/GitNexus/actions/workflows/ci.yml/badge.svg" alt="CI Workflows"/>
  21. </a>
  22. </p>
  23. </div>
  24. GitNexus indexes a codebase into a knowledge graph of symbols, calls, dependencies
  25. and execution flows. Use it through your coding agent's MCP tools, the CLI, or a
  26. web graph explorer.
  27. [Quick start](#quick-start) · [Documentation](#documentation) ·
  28. [Web UI](https://gitnexus.vercel.app) · [Discord](https://discord.gg/MgJrmsqr62)
  29. https://github.com/user-attachments/assets/172685ba-8e54-4ea7-9ad1-e31a3398da72
  30. ## Quick start
  31. Requires **Node.js 22.18+ on 22.x, or 24.11+**. See [platform requirements](gitnexus/README.md#requirements)
  32. for Linux and Windows native dependencies.
  33. ```bash
  34. # Run from your repository root
  35. npx gitnexus analyze
  36. # Connect your editors once
  37. npx gitnexus setup
  38. ```
  39. `analyze` builds the index, installs agent skills, registers Claude Code hooks,
  40. and writes `AGENTS.md` / `CLAUDE.md` context files. `setup` configures MCP for your
  41. editors. Use `gitnexus analyze --index-only` to index without those repository
  42. integration files.
  43. For repeated use, install globally with `npm install -g gitnexus`.
  44. If installation fails, see [troubleshooting](gitnexus/README.md#troubleshooting).
  45. ## What you can do
  46. | Task | Tool |
  47. | ------------------------------------------- | ---------------- |
  48. | Find code and related execution flows | `query` |
  49. | Inspect a symbol's callers and dependencies | `context` |
  50. | Check what a change could affect | `impact` |
  51. | Trace a path between two symbols | `trace` |
  52. | Review the impact of a Git diff | `detect_changes` |
  53. | Preview and apply a semantic rename | `rename` |
  54. Ask your agent questions such as “What calls this function?” or “What would this
  55. change affect?” Resolution depends on language support and available evidence;
  56. check reported ambiguity, index freshness and coverage limits.
  57. ## Editor setup
  58. `gitnexus setup` detects Claude Code, Cursor, Codex, Antigravity, Factory Droid,
  59. OpenCode, CodeBuddy and Qoder. Windsurf requires manual MCP configuration.
  60. To select editors:
  61. ```bash
  62. gitnexus setup -c cursor,codex
  63. ```
  64. See [editor setup](docs/editor-setup.md) for the support matrix, manual MCP
  65. configuration, hooks and plugin installation.
  66. ## Everyday commands
  67. ```bash
  68. gitnexus analyze # Refresh the current repository's index
  69. gitnexus analyze --watch # Reindex as local files change
  70. gitnexus query "authentication" # Search the graph
  71. gitnexus impact UserService --direction upstream
  72. gitnexus status # Check index freshness
  73. gitnexus list # List indexed repositories
  74. gitnexus serve # Serve indexed repositories to the web UI
  75. ```
  76. For multiple concurrent agents, use one `gitnexus mcp --http --port 3111` server
  77. and connect clients to `http://127.0.0.1:3111/mcp`. See the
  78. [shared-server instructions](docs/cli-reference.md#multi-client-setups-use---http-not-stdio).
  79. ## Web UI
  80. Run `gitnexus serve`, then open [gitnexus.vercel.app](https://gitnexus.vercel.app).
  81. The UI connects to the backend to browse indexed repositories and use AI chat.
  82. It uses the existing index; no re-upload or re-index is needed.
  83. <img width="1280" alt="GitNexus graph explorer" src="https://github.com/user-attachments/assets/cc5d637d-e0e5-48e6-93ff-5bcfdb929285" />
  84. For Docker, hosted deployments, image verification, or a local frontend, see
  85. [deployment](docs/deployment.md).
  86. ## Supported languages
  87. C, C++, C#, COBOL, Dart, Go, Java, JavaScript, Kotlin, Objective-C, PHP, Python,
  88. Ruby, Rust, Swift, TypeScript, Vue and Zig have registered providers. Support
  89. varies by construct; see the [language inventories](docs/languages/README.md)
  90. for measured behavior, exclusions and remaining gaps.
  91. ## Documentation
  92. <a id="cli-reference"></a>
  93. <a id="environment-variables"></a>
  94. <a id="vector-cutoff-tuning"></a>
  95. | Read | For |
  96. | ---------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------- |
  97. | [CLI reference](docs/cli-reference.md) | Commands, indexing flags, watch mode, configuration and shared stores |
  98. | [Environment variables](docs/cli-reference.md#environment-variables) · [vector tuning](docs/cli-reference.md#vector-cutoff-tuning) | Runtime settings and search tuning |
  99. | [MCP reference](docs/mcp-reference.md) | All tools, resources, examples, policies and response budgets |
  100. | [Editor setup](docs/editor-setup.md) | Supported integrations and manual configuration |
  101. | [Deployment](docs/deployment.md) | Docker, Render, image signatures and local frontend setup |
  102. | [Wiki generation](docs/wiki-generation.md) | Model configuration and generated repository documentation |
  103. | [Runbook](RUNBOOK.md) | Index recovery, embeddings and operational troubleshooting |
  104. | [Architecture](ARCHITECTURE.md) · [type resolution](type-resolution-system.md) | How the indexer and resolution layers work |
  105. | [Type-resolution roadmap](type-resolution-roadmap.md) | Planned work and acceptance criteria |
  106. ## Security and privacy
  107. The CLI indexes code locally without an LLM. Optional remote embeddings, wiki
  108. generation and AI chat use the providers you configure. The web UI accesses the
  109. backend it connects to. Review [security guidance](SECURITY.md) and
  110. [deployment authentication](docs/deployment.md#deploy-to-render) before exposing
  111. an index to other users.
  112. ## Development
  113. See [CONTRIBUTING.md](CONTRIBUTING.md) for setup and pull requests,
  114. [TESTING.md](TESTING.md) for validation, and [GUARDRAILS.md](GUARDRAILS.md) for
  115. repository rules.
  116. ## Enterprise
  117. GitNexus is available as an **enterprise offering** — fully managed **SaaS** or **self-hosted** deployment. Commercial use of the OSS version is also available with proper licensing.
  118. Enterprise includes:
  119. - **PR Review** — automated blast radius analysis on pull requests
  120. - **Auto-updating Code Wiki** — always up-to-date documentation (Code Wiki is also available in OSS)
  121. - **Auto-reindexing** — knowledge graph stays fresh automatically
  122. - **Multi-repo support** — unified graph across repositories
  123. - **OCaml support** — additional language coverage
  124. - **Priority feature/language support** — request new languages or features
  125. **Upcoming:** auto regression forensics · end-to-end test generation
  126. 👉 Learn more at [akonlabs.com](https://akonlabs.com) — for commercial licensing or enterprise inquiries, ping us on [Discord](https://discord.gg/AAsRVT6fGb) or email founders@akonlabs.com
  127. ## Community Integrations
  128. Built by the community — not officially maintained, but worth checking out.
  129. | Project | Author | Description |
  130. | ----------------------------------------------------------------------------- | ------------------------------------------------------ | ----------------------------------------------------------------------- |
  131. | [pi-gitnexus](https://github.com/tintinweb/pi-gitnexus) | [@tintinweb](https://github.com/tintinweb) | GitNexus plugin for [pi](https://pi.dev) — `pi install npm:pi-gitnexus` |
  132. | [gitnexus-stable-ops](https://github.com/ShunsukeHayashi/gitnexus-stable-ops) | [@ShunsukeHayashi](https://github.com/ShunsukeHayashi) | Stable ops & deployment workflows (Miyabi ecosystem) |
  133. | [KiloCode MCP workflow](Documentation/kilo-code-mcp.md) | [@oktanishq](https://github.com/oktanishq) | Guide to connect GitNexus MCP to Kilo Code and verify tools. |
  134. > Have a project built on GitNexus? Open a PR to add it here!
  135. ## License
  136. [PolyForm Noncommercial 1.0.0](LICENSE). Commercial licensing is available through
  137. [akonlabs.com](https://akonlabs.com).
  138. ## Acknowledgments
  139. - [Tree-sitter](https://tree-sitter.github.io/) — AST parsing
  140. - [LadybugDB](https://ladybugdb.com/) — embedded graph database with vector support (formerly KuzuDB)
  141. - [Sigma.js](https://www.sigmajs.org/) — WebGL graph rendering
  142. - [transformers.js](https://huggingface.co/docs/transformers.js) — browser ML
  143. - [Graphology](https://graphology.github.io/) — graph data structures
  144. - [MCP](https://modelcontextprotocol.io/) — Model Context Protocol

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.