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

vibelint

v0.1.0

Published

Linter and analyzer for AI-assisted coding sessions

Readme

vibelint

Lint and analyze AI-assisted coding sessions from the command line.

vibelint inspects your current repository plus local Claude Code session data and reports configuration issues, session quality patterns, and model-usage signals.

Install

Run without installing:

npx vibelint

Or install globally:

npm install -g vibelint
vibelint

Usage

Run it directly with npx:

npx vibelint

Useful flags:

npx vibelint --static
npx vibelint --json
npx vibelint --last 5
npx vibelint --session <id>
npx vibelint --cost

Typical local workflow:

cd /path/to/your/repo
npx vibelint --static
npx vibelint --last 5

Requirements

  • Node.js 20 or newer
  • A repository you want to inspect
  • Local Claude Code data in ~/.claude for session-based analysis

If no Claude Code sessions are available, vibelint can still run static checks with --static.

What It Checks

  • Project config quality
  • Claude Code permission settings
  • Repository context and command coverage
  • Conversation efficiency and output quality
  • Model-choice mismatch and cost signals
  • Cross-session trends

Output Modes

  • Default terminal report for interactive use
  • --json for CI, scripts, and piping
  • --static to avoid session-based analysis
  • --cost to focus on model-usage and spend signals

Publish Checklist

Before publishing:

npm test
npm run build
npm pack --dry-run

The published package is expected to contain only the built CLI in dist/ plus package metadata and docs.