Skip to content
PluginStats

@nanonets/graft weekly downloads statistics

By nanonets · npm · MCP servers

Build a repo's context graph as a folder of linked markdown files: a local, regenerable cache that every query keeps in sync with your code.

View on npm Fresh · Nov 3, 2026

@nanonets/graft has 30,279 recorded weekly downloads on npm, a decrease of 10.8% over the past 30 days, ranking #882 of 2,762 tracked listings.

Weekly downloads
30,279
Official API · Nov 1, 2026
7-day growth
+115%
+16.2K weekly downloads
30-day growth
-10.8%
-3.7K weekly downloads
90-day growth
+2303%
+29K weekly downloads
Rank
#882
Among tracked npm listings

About @nanonets/graft

<div align="center"> <picture> <source media="(prefers-color-scheme: dark)" srcset="assets/trail-code-banner-dark.png"> <img src="assets/trail-code-banner.png" alt="Trail-code (previously graft), by Trail. A map of a codebase, with one team decision pinned to it: keep retries at 4." width="100%"/> </picture>
The self-learning context layer for coding agents.

Trail-code gives Claude Code, Cursor, Codex and other coding agents a map of your code, and what your team has learned about it.

Code map (previously graft)Learnings
What is it?An index of your code: every function and who calls it, so your agent sees what a change can breakWhat you, your agents and your team have learned and decided
What does it do for your agent?Takes it straight to the right filesLets it pick up where you and your team left off
Where does it come from?Your code, read on your machineYour conversations, as you work

<a href="https://trendshift.io/repositories/92209?utm_source=trendshift-badge&utm_medium=badge&utm_campaign=badge-trendshift-92209" target="_blank" rel="noopener noreferrer"><img src="https://trendshift.io/api/badge/trendshift/repositories/92209/daily?language=TypeScript" alt="trailhq/Trail-Code | Trendshift" width="250" height="55"/></a>

<p> <a href="https://github.com/trailhq/Trail-Code"><img src="https://img.shields.io/github/stars/trailhq/Trail-Code?style=for-the-badge&logo=github&logoColor=white&label=Star%20on%20GitHub&color=FFC83D" /></a> <a href="https://trailhq.com/graft"><img src="https://img.shields.io/badge/website-trailhq.com/graft-E5484D?style=for-the-badge" /></a> <a href="https://discord.gg/zxmKweAA29"><img src="https://img.shields.io/badge/Discord-join-5865F2?style=for-the-badge&logo=discord&logoColor=white" /></a> <a href="https://www.npmjs.com/package/@trailhq/trail-code"><img src="https://img.shields.io/npm/v/%40trailhq%2Ftrail-code?style=for-the-badge&logo=npm&logoColor=white&label=npm" /></a> <a href="https://www.npmjs.com/package/@nanonets/graft"><img src="https://img.shields.io/npm/dm/%40nanonets%2Fgraft?style=for-the-badge&logo=npm&logoColor=white&label=downloads" /></a> <a href="https://nodejs.org"><img src="https://img.shields.io/node/v/%40trailhq%2Ftrail-code?style=for-the-badge&logo=nodedotjs&logoColor=white" /></a> <img src="https://img.shields.io/badge/TypeScript-strict-3178C6?style=for-the-badge&logo=typescript&logoColor=white" /> <img src="https://img.shields.io/badge/License-MIT-20C997?style=for-the-badge" /> <a href="TELEMETRY.md"><img src="https://img.shields.io/badge/telemetry-anonymous%2C%20opt--out-546FFF?style=for-the-badge" /></a> <a href="https://scorecard.dev/viewer/?uri=github.com/trailhq/Trail-Code"><img src="https://img.shields.io/ossf-scorecard/github.com/trailhq/Trail-Code?style=for-the-badge&label=openssf%20scorecard" /></a> </p>
46% fewer tool calls, 60% less time, and more real issues solved.
Cold agentAgent with the graft map
Tool calls, 162 runsbaseline46% fewer
Uncached input tokens, 162 runsbaseline42% fewer
Time, 162 runsbaseline60% less
SWE-bench Verified, 50 real issues27 solved (54%)33 solved (66%)
npm install -g @trailhq/trail-code && trail init
</div>

[!NOTE] Graft is now Trail-code. Graft lives on as the graft map, and every graft command still works. What's new is learnings. What changed

<p align="center"> <picture> <source media="(prefers-color-scheme: dark)" srcset="assets/trail-code-how-it-works-dark.webp"> <img src="assets/trail-code-how-it-works.webp" alt="Without Trail: each task starts a new session with an agent that has no memory. It searches blind, opens the wrong files, guesses how the code is wired, ships the task, and the context is lost. This repeats for every task and every teammate's agent. With Trail, your agent already knows your code: trail init builds the graft map, a hook points the agent to it before each session, the agent reads the graph with its impact radius, gets precise context, ships the task, then saves learnings. One graph, every agent, up to 4x tokens saved." width="880"/> </picture> </p>

What changes in your agent

Without Trail-codeWith Trail-code
Greps and opens file after file to find the code it needsGets the right files and functions with your prompt
Re-explores code a teammate already figured out last weekStarts from their learning: what they decided, what they ruled out, what to watch out for
Undoes a teammate's decision, because it never knew about ittrail check flags it before the PR, quoting who decided it and why
Finds out at merge time that a teammate changed the same codeSays so right after it edits code a teammate's open branch also changes, and whether the two clash
Has to be told the same things every sessionStarts from what you've told it before: trail init finds what you said more than once in your past sessions
You write and update CLAUDE.md by handLearnings are saved from your conversations, in files you can read

Same model, more tasks solved. On SWE-bench Verified (real GitHub issues, graded by the maintainers' own tests), Claude Sonnet 5 solved 33 of 50 issues with the graft map and 27 of 50 without it, using 23% fewer tokens. Details

Cheaper and faster. Across 162 runs of the same agent on the same tasks: 32% lower cost, 42% fewer uncached input tokens, 60% less time, and the same share of correct answers. On PocketBase, 15 real tasks ran 21% cheaper and 14% faster. Details


Contents…

Description from the npm listing.

  • mcp
  • mcp-server
  • model-context-protocol
  • claude-code
  • cursor
  • ai
  • agents
  • knowledge-graph
  • context
  • codebase
  • llm
  • graft

README badge

Show your rank in a README or on your website. The badge updates automatically.

Charts

Images: 30d · 1y · all time · 1600×900 dark

Adoption over time

@nanonets/graft weekly downloads on npm, last 90 days: 30,279 weekly downloads as of Nov 1, 2026, +2303% over 90 days.@nanonets/graftWeekly downloads on npm · Last 90 days30,279downloads / week+2303% over 90 days05K10K15K20K25K30K35KAug 3Aug 18Sep 2Sep 17Oct 2Oct 17Nov 1downloads / weekobservedarchived (Internet Archive)no observationsAug 5, 2026 – Nov 1, 2026 · 89 observations · Updated Nov …pluginstats.com
@nanonets/graft weekly downloads on npm, last 90 days: 30,279 weekly downloads as of Nov 1, 2026, +2303% over 90 days.

7/30/90-day growth

@nanonets/graft weekly downloads growth on npm: +115% over 7 days, -10.8% over 30 days, +2303% over 90 days.@nanonets/graftWeekly downloads growth on npm30,279downloads / week now7-day growth+16,228 weekly downloads+115%30-day growth-3,662 weekly downloads-10.8%90-day growth+29,019 weekly downloads+2303%Growth vs. nearest observation to each baseline date · Updated Nov 1, 2026pluginstats.com
@nanonets/graft weekly downloads growth on npm: +115% over 7 days, -10.8% over 30 days, +2303% over 90 days.

Ranking history

@nanonets/graft npm ranking history: currently #882 (by weekly downloads).@nanonets/graftnpm ranking · by weekly downloads · Last 90 days#882current rank#880#882#884#886#888#890#892#894Aug 5Aug 20Sep 4Sep 19Oct 4Oct 19Nov 3rankOct 31, 2026 – Nov 3, 2026 · 4 observations · Updated Nov 1, 2026pluginstats.com
@nanonets/graft npm ranking history: currently #882 (by weekly downloads).

Listing placement

All npm2,762 listings · 139 pages · 1,383 shown · page 45, #2 (overall #882)
All npm: every listing in weekly downloads order

Listing placement

MCP servers376 listings · 19 pages · page 7, #17 (overall #137)
MCP servers: every listing in weekly downloads order

Filled points are observed values; hollow points come from Internet Archive snapshots of the listing page. Dashed segments span periods with no observations — values between points are not interpolated.

Each band is one page of 20. Weekly downloads on a linear scale. Placement is projected from weekly downloads, so it can differ from the marketplace's own sort order. Hover a dot to see the listing.

Recent observations

Full history (122)
Recent weekly downloads observations for @nanonets/graft
Date (UTC)Weekly downloadsChange vs. previous
30,279+7.3K
22,980-2.4K
25,357-4.2K
29,517-1.5K
31,056+4.1K
26,976+8.6K
18,414+4.4K
14,051+100
13,951+341
13,610-97
13,707+5.5K
8,2500
8,2500
8,250—

Similar npm MCP servers plugins

All 20 @nanonets/graft alternatives

Data source

Weekly downloads (trailing 7 complete days) come from the official npm downloads API. Downloads include CI and mirrors and are not equivalent to installs or users. npm publishes no ratings.

Listing: https://www.npmjs.com/package/@nanonets/graft. First seen Oct 31, 2026; last successful collection Nov 3, 2026. See the methodology.