Ext Ops Panel
Open dashboard
Comparison

scan-modules vs graperoot

scan-modules is a plugin bundle for AI coding tools published by fengzhyuan. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). graperoot is a plugin bundle for AI coding tools published by kunal12203. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-13. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacescan-modulesgraperoot
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 3.8.66
Forks (GitHub): 3
Stars (GitHub): 15
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

scan-modules vs graperoot
Factscan-modulesgraperoot
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)15 (better)
Forks (GitHub) (differs)0 (worse)3 (better)
Last releaseNot publishedNot published
Where it runsInstalls as a plugin bundleInstalls as a plugin bundle
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 0
Hooks it runs (differs)1Not published
Parts of the bundle (differs)32
Licence (differs)MITProprietary
Repository (differs)github.com/fengzhyuan/scan-modules-plugingithub.com/kunal12203/graperoot-plugin
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

scan-modules

In its own words, on Claude Code: claude-plugins-community:

Scan and cache project module structure for fast Claude context loading. Use /scan-modules:scan-modules to index your codebase, then Claude auto-loads the cache each session. Supports incremental updates via git diff and auto-update via post-commit hook. Works with Swift, TypeScript, Python, Go, and Rust.

graperoot

In its own words, on Claude Code: claude-plugins-community:

Dual-graph code context engine for Claude Code. Builds a structural call graph and dependency graph of your codebase, then delivers precise file and symbol recommendations before Claude starts exploring. Reduces token usage by up to 60% and improves code accuracy by guiding Claude to the right files first. Supports TypeScript, JavaScript, Python, Go, Rust, Java, C/C++, and 10+ more languages. Install via pip, no source code required, fully compiled

How to run each

scan-modules As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install scan-modules@claude-community

graperoot As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install graperoot@claude-community

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of scan-modules publish no settings it asks for, so we do not compare settings.

What it can do: scan-modules · What it can do: graperoot · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built