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

nogrep

v1.2.2

Published

Navigable codebase index for Claude Code — stop grepping, start navigating

Readme

nogrep

A Claude Code plugin that gives AI agents a navigable index of any codebase, so they stop doing blind grep/find exploration.

What it does

nogrep generates a structured .nogrep/ directory with a reverse index and thin context nodes (markdown files). When you need Claude Code to find something, run /nogrep:query — it reads 2 context files instead of running 20 grep commands.

Install

In Claude Code:

  1. Type /plugin and go to the Marketplaces tab
  2. Hit Enter on + Add Marketplace and enter alirezanasseh/nogrep
  3. Wait for the plugin to appear, then hit Enter on nogrep
  4. Choose the installation scope (you, your team, etc.) and hit Enter
  5. Type /reload-plugins to activate

Quick start

  1. Open your project in Claude Code
  2. Run /nogrep:init — Claude analyzes your codebase and generates the index
  3. Ask questions with /nogrep:query where is auth handled?

How it works

Phase 1: Collect signals    (scripts — file tree, deps, git churn, entry points)
Phase 2: Detect stack       (Claude — language, frameworks, domain clusters)
Phase 3: Analyze clusters   (Claude — per-domain context nodes from trimmed source)
Phase 4: Write index        (scripts — .nogrep/ files, _index.json, CLAUDE.md patch)

Scripts handle data collection and file I/O. Claude does all the analysis work directly during the session — no API keys needed.

Commands

| Command | Description | |---------|-------------| | /nogrep:init | Generate the full codebase index | | /nogrep:update | Incrementally update stale nodes | | /nogrep:query <question> | Query the index, read matched context files, and get an answer | | /nogrep:status | Show index health and freshness | | /nogrep:on | Enable nogrep | | /nogrep:off | Disable nogrep |

Output structure

.nogrep/
├── _index.json        # reverse index (tags → files, keywords → files, paths → context)
├── _registry.json     # source path → context file mapping
├── _taxonomy.json     # allowed tags for this project
├── domains/           # one file per business domain
├── architecture/      # cross-domain architectural concerns
├── flows/             # multi-domain business flows
└── entities/          # data models

Each context node is a thin markdown file with YAML frontmatter — purpose, public surface, gotchas, and tags. Nodes include a ## Manual Notes section that is never overwritten by updates.

Settings

nogrep stores its enabled state in your project's .claude/ directory:

  • .claude/settings.json — team settings (commit to repo)
  • .claude/settings.local.json — personal overrides (gitignored)

Contributing

Source code lives on the develop branch. The main branch contains only the built plugin and is updated automatically by CI on every push to develop.

git clone -b develop https://github.com/alirezanasseh/nogrep
cd nogrep
npm install
npm run build
npm test

Requirements

  • Node.js 20+
  • Claude Code

License

MIT