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

@harshalpatel2868/vibe-check

v1.0.2

Published

A vibe check for your code

Downloads

312

Readme

🧠 VibeCheck CLI

"Check yourself before you vibe code yourself."

A real-time checkpoint layer that intercepts every AI agent decision, translates it to plain English, and asks for your approval before anything executes.

🎯 The Problem

Hundreds of millions of people are vibe coding in 2026. AI agents make hundreds of decisions per session — restructuring files, adding dependencies, modifying databases, touching secrets — without ever asking. Students and beginners ship applications they don't understand, can't maintain, and can't fix when they break.

No simple, automated tool exists to give them visibility and control. VibeCheck is that tool.

Install with npm install -g @harshalpatel2868/vibe-check — zero AI, zero API keys, works offline forever.

🚀 Installation

Install globally using npm:

npm install -g @harshalpatel2868/vibe-check

Zero AI dependencies. No API keys. No internet required. Works offline forever.

💻 Quick Start

Navigate to your project folder and start the watcher:

cd your-project
vibecheck start

Now, just leave this terminal open and go write code with your favorite AI agent (Claude Code, Cursor, Copilot, etc.). Every time the AI tries to make a change, VibeCheck intercepts it!

🛠️ Commands

| Command | Description | | --------------------------- | ------------------------------------------------------------ | | vibecheck start | Starts watching the current directory for AI changes | | vibecheck log | Shows a color-coded log of all decisions (approved/rejected) | | vibecheck log --today | Shows logs only from today's session | | vibecheck log --rejected | Shows only the changes you rejected | | vibecheck summary | Generates a clean session summary of what the AI built | | vibecheck rollback <id> | Rolls back a specific decision by ID | | vibecheck rollback --last | Undoes the last approved decision |

⚙️ Configuration

VibeCheck creates a .vibecheck/config.json file in your project root. You can customize the behavior here:

{
  "autoApproveThreshold": ["INFO", "LOW"],
  "ignoredPatterns": [],
  "severityOverrides": {}
}

You can also create a .vibecheckignore file (like .gitignore) in your root directory to ignore specific files or folders.

🧩 The Pattern Library

VibeCheck works by matching simple and complex changes against a known library of patterns.

Severities:

  • INFO / LOW: Auto-approved (like adding comments or simple functions)
  • MEDIUM: Pauses and prompts (like adding dependencies or using localStorage)
  • HIGH: Pauses and warns (like touching API keys or md5 hashing)
  • DANGER / CRITICAL: Sirens blaring (like dropping tables or deleting secure data)

Contributing new patterns

Want to add patterns for a specific framework? It's simple! Check out the src/patterns/ directory.

Example src/patterns/general.js addition:

{
  match: /app\.listen\(/,
  severity: 'LOW',
  message: "AI is starting a web server"
}

📜 License

MIT © 2026 Harshal Patel — free to use, modify, and distribute.