DevIndex – Ranking 50k GitHub developers using a static JSON file
Client-side ranking of 50k developers with zero backend—clever constraint engineering.
Static analysis engine that maps any codebase into ranked, token-budgeted context — offline, zero LLM cost
Two-pass scanner prunes folders before reading files, but keyword patterns beat structural analysis.
Developers working with unfamiliar codebases or building LLM code analysis tools
Cursor · Continue · Sourcegraph Cody
It's a static analysis engine that: - Walks the repo in two passes (no unnecessary file reads) - Builds an import graph across 9 languages to rank files by importance - Assembles a token-budgeted context map in under 10 seconds - Works fully offline, no API key needed
I've tested it on Next.js and gemini-cli. It's not perfect — pattern detection is keyword-based not structural, and monorepo support is limited. Happy to discuss the tradeoffs.
Would genuinely love feedback on the engineering approach or anything that seems wrong/naive.
Install:pip install context-engine-cli
Client-side ranking of 50k developers with zero backend—clever constraint engineering.
Anti-algorithm news feed manifesto, but lacks a working submission mechanism or active feed.
98% context reduction for AI agents—measured on real projects.
MCP query server cuts codebase context by 87% with zero dependencies, measured.
ESLint for system design: catch architecture violations in CI before code review becomes bottleneck.
Static heuristics beat running actual agents for scoring repo readiness.