npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@ctxo/cli

v0.8.1

Published

MCP server delivering dependency-aware, history-enriched context for codebases

Readme

npm version CI Release

npx @ctxo/init
npx @ctxo/cli index

Detects your languages, installs the right plugins, wires Ctxo into your AI client, installs git hooks, and builds the first index one command.


The Problem: agents code blind

Drop a modern coding agent into a real repo. It ripgreps a symbol, gets 47 hits, reads five files to find the definition, five more for callers misses the subclass entirely (inheritance doesn't show up in text search), never checks git history (and confidently reintroduces a bug that was reverted three weeks ago), then runs out of context and starts hallucinating.

It's not a skill gap. It's a sensory gap. The agent is navigating your codebase with its eyes closed and a phone book.

The Solution: proactive, not reactive

The core shift: your agent stops reacting to files it stumbles into and starts planning from a complete map. Blast radius before the edit. Git intent before the bug fix. Importer list before the rename.

Ctxo indexes your repo once kept fresh by file watchers and git hooks into a deterministic graph: every symbol, every edge (imports, calls, extends, implements), every relevant git commit with intent classified, every anti-pattern. All exposed through 14 semantic MCP tools.

One get_blast_radius call replaces an entire ripgrep/read spiral. One get_pr_impact replaces a full review session of "wait, what calls this?"

The agent still writes the code. It just stops writing it blind so the bug never has to be caught by the compiler, the tests, CI, or a user.

Codebase Dashboard

Full-stack analytics UI with eight views: File Tree, Heatmap, Co-Changes, Timeline, Architecture, MCP Explorer, and Diff. Deployed to GitHub Pages on every push.

Codebase Dashboard

Open Dashboard

Dependency Graph

ctxo visualize generates a self-contained HTML from your .ctxo/ index. Interactive force-directed graph with PageRank sizing, layer coloring, blast radius on click, and dark/light theme.

Dependency Graph

Open Dependency Graph

Links

License

MIT