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

print_check

v1.2.5

Published

A Git pre-commit hook that detects and prevents print/debug statements from being committed

Readme

print_check

A Git pre-commit hook that detects and prevents print/debug statements from being committed to your repository.

Features

  • Automatically scans staged files for print/debug statements before commits
  • Configurable file extensions and search patterns
  • Optional warning mode vs blocking mode
  • Interactive setup with saved configuration
  • Preserves existing pre-commit hooks
  • Shows line details for detected statements (optional)

Installation

npm install -g print_check

Or install as a dev dependency in your project:

npm install --save-dev print_check

Usage

Run the command in your git repository:

print_check

On first run, you'll be prompted to configure:

  • File extensions to check (e.g., .js,.ts,.jsx,.tsx)
  • Search patterns (e.g., console.log,console.error,debugger)
  • Warning mode (allow commit with confirmation) or blocking mode (prevent commit)
  • Whether to show line details for each detected statement

Your configuration will be saved to print_check_config.json in your project root.

Setup as Pre-commit Hook

To automatically run print_check before every commit, you can:

1. Just follow the setup by running print_check after downloading.

2. After completing the setup phase any terms found matching your search patterns will be flagged.

Configuration

Example print_check_config.json:

{
  "fileExtensions": [".js", ".ts", ".jsx", ".tsx"],
  "warnOnly": false,
  "searchTerms": ["console.log", "console.error", "debugger"],
  "hasLineDetails": true
}
  • fileExtensions: Array of file extensions to check
  • warnOnly: If true, prompts for confirmation; if false, blocks the commit
  • searchTerms: Array of patterns to search for
  • hasLineDetails: If true, shows line numbers and content for each match

Requirements

  • Node.js >= 18.0.0
  • Git repository

License

MIT