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

houndlens

v2.4.2

Published

Give your AI the full picture. Save your tokens.

Downloads

1,507

Readme

houndlens

Give your AI the full picture.

houndlens analyzes your project in milliseconds and gives AI everything it needs — structure, dependencies, and verified results from your project's own tools.

Install

npm install -g houndlens

Use

cd your-project
houndlens                    # analyze project (10ms)

Then tell your AI: let's start houndlens

What it does

1. Instant project analysis

houndlens parses every file, builds a call graph, and outputs a lightweight summary for AI.

.houndlens/summary.json (3KB) — project structure, dependencies, health
.houndlens/changes.json       — what changed since last scan

AI reads these instead of opening files one by one.

2. AI runs all checks for you

When AI modifies code, it runs houndlens verify which executes your project's own tools on changed files:

houndlens verify --diff HEAD

  [houndlens] syntax: 0 errors
  [tsc] type check: 1 error — auth.ts:42 missing argument
  [eslint] lint: 0 warnings
  
  1 error total

One command. All tools. Only changed files.

3. AI ↔ houndlens verification loop

Claude Code — automatic ping-pong:

AI modifies auth.ts
  → hook fires automatically
  → houndlens verify runs (tsc + eslint on auth.ts only)
  → result injected into AI's conversation: "auth.ts:42 missing argument"
  → AI fixes auth.ts
  → hook fires again → 0 errors
  → done

AI doesn't choose to verify — it's forced by the hook.

Other AI tools (Cursor, Gemini, Codex, etc.) — instruction-based:

AI modifies auth.ts
  → AI follows ai-instructions.md
  → runs houndlens verify
  → reads result, fixes errors

Works when AI follows instructions. Not guaranteed.

4. Commit protection

All AI tools — git pre-commit hook blocks broken code. No exceptions. Even if AI skipped verification, broken code cannot be committed.

Supported languages

Rust · TypeScript · JavaScript · Python

Performance

| Project | Analysis | |---------|----------| | 10 files | ~10ms | | 100 files | ~100ms | | 1000 files | ~1s |

Verification time depends on your project's tools (tsc, eslint, etc.)

License

Apache-2.0 OR MIT