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

git-safe-push

v1.0.2

Published

A lightweight CLI tool that scans staged Git files before push and prevents dangerous code from being pushed accidentally.

Readme

git-safe-push

npm npm npm version license

A lightweight CLI tool that scans staged Git files before push or commit and prevents dangerous code from being pushed accidentally.

Installation

npm install -g git-safe-push

Quick Start

# Scan staged files
npx git-safe-push

# Install git hooks (auto-scan on push & commit)
npx git-safe-push install

CLI Usage

Scan before push

$ npx git-safe-push

  🔍 Scanning before push...

  ❌ Found console.log in:
    src/auth.js
    → console.log("login failed")

  ❌ Found debugger statement in:
    app.js
    → debugger;

  ⚠ Found TODO comment in:
    src/routes.js
    → // TODO: add validation

  ❌ Push blocked for safety.

Install hooks

npx git-safe-push install
# ✅ pre-push hook installed
# ✅ pre-commit hook installed

Now every git push and git commit will automatically scan staged files. If dangerous content is found, the push/commit is blocked.

Configuration

Create git-safe-push.config.json in your project root:

{
  "block": [
    "console.log",
    "debugger",
    "API_KEY",
    "fdescribe(",
    "fit(",
    "only("
  ]
}

What It Detects

| Severity | Pattern | Example | | -------- | ------------------------- | -------------------------------- | | ❌ Error | console.log/warn/error | console.log("debug") | | ❌ Error | debugger statement | debugger; | | ❌ Error | Possible API keys | sk-abc... or long string | | ❌ Error | Hardcoded password | password: "secret" | | ❌ Error | Hardcoded secret/token | secret: "123" | | ⚠ Warn | TODO comments | // TODO: fix me | | ⚠ Warn | .env references | .env in code | | ⚠ Warn | process.env usage | process.env.PORT |

Test

node test.js

License

MIT