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

geto-graph

v0.3.0

Published

SQLite + BM25 codebase symbol graph for pi. Query-first reading: search, refs, blast radius.

Readme

geto-graph

SQLite + BM25 codebase symbol graph for pi. Agents query the graph instead of guessing how the codebase is connected — then read only what's necessary.

Part of the geto monorepo.

Install

Via pi (npm package)

pi install npm:[email protected]

From source (this monorepo)

npm install                            # from repo root (links workspaces)
node packages/geto-graph/scripts/download-grammars.mjs   # fetch tree-sitter .wasm grammars
ln -s "$PWD/packages/geto-graph" ~/.pi/agent/extensions/geto-graph   # global
# or: ln -s "$PWD/packages/geto-graph" .pi/extensions/geto-graph      # project-local

Then /reload in pi. The index auto-builds (lazily) on first geto_graph_* tool call for the current project, stored in <project>/.geto-graph/index.db (add .geto-graph/ to your project's .gitignore).

Requires pi >= 0.84 (declared as a peer dependency).

Commands

  • /geto-graph status — index size/freshness
  • /geto-graph reindex [--force] [path] — incremental (mtime/size) or forced full reindex

Tools

| Tool | Purpose | |---|---| | geto_graph_search | BM25 symbol search (name/signature/doc) | | geto_graph_symbol | Exact lookup, all definitions across files | | geto_graph_refs | Direct edges in/out: calls, imports, extends, implements, uses | | geto_graph_file | All symbols + imports + config keys of one file | | geto_graph_overview | Per-file symbol counts — the map | | geto_graph_blastradius | BFS impact analysis (reverse/forward, depth, scope) | | geto_graph_index | Incrementally refresh changed files and report additions plus persisted totals | | geto_graph_reindex | Force a full index rebuild | | geto_graph_status | Index freshness |

Supported files

  • .ts/.tsx/.js/.jsx/.mts/.cts — tree-sitter (WASM) full symbol + call/type/import graph
  • .yaml/.yml — structural key-path scanner (services.web.image)
  • Dockerfile/Containerfile — instruction scanner

Dev

npm test                                           # isolated regression checks
npm run test:e2e -- <project-root>                 # index a real project + run all queries

Releases

Versions, changelogs, tags, and npm publication are managed by Release Please from Conventional Commits. Do not edit the package version manually.

Notes

  • Parse-extract-free per file: memory stays flat regardless of repo size (~1MB for 4000 files). Per-file ceiling is ~35MB (wasm32); files over 20MB are skipped.
  • .geto-graph/ should be gitignored.
  • Requires pi >= 0.84 (declared as a peer dependency).