scheidydude/codeindex

Score8.0

Popularity261.0

Risknone

TierGold

Score breakdown

Usefulness9.0

Novelty8.0

Momentum7.0

Maturity8.8

Open-source/build8.4

Evidence8.0

Workflow potential9.1

Setup ease8.8

Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.

Why it matters

Useful for **AI coding agents that need to know 'what breaks if I change this'** — `codeindex impact src/auth.py` returns the blast-radius score (how many files break if this one changes) with historical as-of queries, so the agent can plan a refactor with a real dependency graph instead of reading every file. Useful for **engineering teams evaluating the cost of a change before merging** — `codei

Who should use it

**AI coding agents that need to know 'what breaks if I change this'** — `codeindex impact src/auth.py` returns the blast-radius score (how many files break if this one changes) with historical as-of queries, so the agent can plan a refactor with a real dependency graph instead of reading every file**Engineering teams evaluating the cost of a change before merging** — `codeindex changed-since v1.2.0` returns the file-level delta between two release tags, and `codeindex impact <file>` returns the blast radius for any file, so a reviewer can size the change and the risk in one CLI run**AI agents that need symbol-level search** — `codeindex search "validate auth token"` returns the functions / classes matching the query with hybrid semantic + keyword + graph expansion, so an agent can find the right function without grep-scanning the codebase**AI coding agents with the MCP server** — 10 MCP tools expose the graph store to Claude Code / Cursor / Codex, so the agent can answer 'what breaks if I change this file' through MCP instead of CLI**Teams that need CLAUDE.md auto-injection** — codeindex writes the dependency index into `codeindex.json` at the repo root, so a Claude Code session can pick up the index as project context**Architecture review / visualization** — `codeindex serve --viz` launches an interactive 2D / 3D graph, dependency matrix, and treemap, so a team can see the dependency structure visually**Pre-commit hooks** — codeindex ships a pre-commit hook that fails the commit if the blast radius exceeds a configurable thresholdEvaluation: `pip install codeindex`, `codeindex analyze ./myrepo`, `codeindex symbols ./myrepo`, `codeindex impact src/auth.py`, `codeindex search "validate auth token"`, `codeindex changed-since v1.2.0`, and `codeindex serve --viz --repo ./myrepo` to launch the visualization UI

Who should skip it

Skip scheidydude/codeindex if the source repository or demo is inactive, unmaintained, or no longer matches the description shown here.

About this signal

scheidydude/codeindex is tracked by RepoRadar as a apache-2.0 temporal code knowled in the scheidydude/codeindex is the Apache-2.0 codeinde section. It was first seen on 2026-06-25 and last updated on 2026-06-25. The current verdict is 'try now' with a Gold tier and easy setup difficulty. scheidydude/codeindex leads on workflow potential (9.1) and practical usefulness (9.0); its lowest signal is momentum (7.0), so factor that in before investing setup time. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.

How this item is evaluated

RepoRadar assigned scheidydude/codeindex a composite score of 8.0 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 261.0 and never affects the composite score or tier. The risk label of 'none' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.

Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.

Risk explanation

No inherent user-impacting risk is flagged from the captured evidence.

Evidence links

github.com

Closest alternatives / related signals

codeindexscheidydudecode-knowledge-graphtemporal-graphblast-radiusimpact-scoringas-of-queriessymbol-search