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

deep-code-research

v0.1.0

Published

LLM-native code research agent that explores ecosystems via hierarchical multi-agent architecture

Readme

Deep Code Research Agent

"Don't just tell me to add error handling. Show me exactly where my code differs from relevant projects."

GitHub stars

Code "literature review" is tedious. Before building something, you should survey similar projects to learn patterns, avoid known pitfalls, and not reinvent wheels. But reading through 10+ related repositories takes hours. This tool does it for you.

Deep Code Research findings with dual-evidence comparison

The only code review that shows your code side-by-side with 10+ similar repos. Generic advice like "add error handling" is useless. This tool produces grounded findings—showing exactly what related repos do differently and where in your codebase to change.

Built on the Claude Agent SDK. See a complete real example output in example_deep_code_research.md.

Setup

# 1. Clone and install
git clone https://github.com/WindChimeRan/deep_code_research.git
cd deep_code_research
npm install
export ANTHROPIC_API_KEY=sk-ant-...

# 2. Run a research
npm run dev https://github.com/user/repo

# Or with options
npm run dev https://github.com/user/repo -- --lens security --budget 50000

Usage

npm run dev https://github.com/user/repo

# With options
npm run dev https://github.com/user/repo -- --lens security --budget 50000

| Option | Description | Default | |--------|-------------|---------| | --lens <focus> | Free-text analysis focus (e.g., "security", "performance", "error handling") | general | | --budget <tokens> | Token budget | 100,000 | | --max-repos <n> | Max related repos to analyze | 20 | | --output <file> | Save JSON report | - |

How It Works

Phase 1: Understand target repo
Phase 1.5: Map target file structure (so sub-agents know what to compare)
Phase 2: Discover related repositories
Phase 3: Sub-agents analyze BOTH repos in parallel, producing comparative evidence
Phase 4: Synthesize TOP 3 grounded findings

Each sub-agent:

  1. Reads the related repo's code
  2. Checks target's file map for equivalent files
  3. Fetches and compares both implementations
  4. Reports the gap: "Target does X, related does Y"

Model Configuration

The tool uses different Claude models for different tasks:

| Role | Model | Why | |------|-------|-----| | Main agent | Opus 4.5 | Complex orchestration, synthesis | | Sub-agents | Haiku 4.5 | Fast, cost-effective for parallel analysis |

To update models (e.g., when newer versions are released), edit src/claude-client.ts:

export const MODEL_ALIASES: Record<ModelAlias, string> = {
  opus: "claude-opus-4-5-20251101",    // ← Update these
  sonnet: "claude-sonnet-4-20250514",
  haiku: "claude-haiku-4-5-20251001",
} as const;

The rest of the codebase uses semantic aliases ("opus", "haiku") so you only need to update this one place.

Cost

A typical research costs $1-3 depending on how many related repos are analyzed. See Anthropic Pricing.

License

MIT