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

greenberries-testbot

v1.0.0

Published

Universal pre-commit/pre-deploy test runner for Greenberries projects.

Readme

greenberries-testbot

Universal pre-commit and pre-deploy test runner for Greenberries projects. Auto-detects project type, runs every layer, blocks commits on any failure.

Install globally (once)

npm install -g /Users/danz0-home/Documents/projects/testbot

Add to a project (30 seconds)

cd ~/Documents/projects/your-project

# 1. Install git hooks
testbot install

# 2. Copy GitHub Actions workflow
mkdir -p .github/workflows
cp ~/Documents/projects/testbot/templates/github/ci.yml .github/workflows/testbot-ci.yml

Done. Every git commit now runs the full gate. Push only happens if CI passes.

What it checks

| Layer | What | Blocks commit | |---|---|---| | secrets | .env files staged, API keys in diff | Yes | | dead-code | debugger, PII in logs, temp files staged | Yes (warn for console.log) | | env-check | .env.example present and in sync | Yes | | audit | npm audit --audit-level=high | Yes | | typecheck | tsc --noEmit or node --check on staged files | Yes | | lint | ESLint with zero warnings | Yes | | unit | npm run test:ci or npm test | Yes | | nextjs-audit | Suspense, SSR safety, metadataBase, netlify.toml | Yes (Next.js only) | | build | npm run build | Yes | | integration | npm run test:integration (if present) | Yes (Node.js API only) |

Commands

testbot                    # run full suite
testbot install            # install .git/hooks/pre-commit and pre-push
testbot uninstall          # remove hooks
testbot --skip=audit,build # skip specific layers
testbot --ci               # CI mode

Skip a layer for one commit

git commit --no-verify     # bypass all hooks (use sparingly)
TESTBOT_SKIP=audit git commit   # not implemented yet - use --no-verify

Per the Greenberries commit convention: always use --no-verify and run tsc + eslint manually first. The hooks are the safety net, not the first line of defense.

Build pipeline integration

GitHub Actions

The workflow in templates/github/ci.yml runs all layers on every push and PR. Copy it into .github/workflows/.

Netlify deploy gate

In your Netlify site settings: Settings > Build & deploy > Deploy notifications > turn on "Deploy to production" only when CI passes. Use the Branch deploys setting to deploy main only after GitHub checks pass (requires enabling "Required status checks" on the branch in GitHub).

Railway deploy gate

Railway auto-deploys on push to main. To gate it:

  1. In GitHub: Settings > Branches > Add rule for main > require status checks to pass
  2. Select testbot / Full test gate as a required check
  3. Railway only sees the push after GitHub allows it through (but Railway triggers independently - use GitHub Actions for Railway deploys instead for true gating)

Adding to a new project (checklist)

  • [ ] testbot install - hooks in .git/hooks/
  • [ ] Copy templates/github/ci.yml to .github/workflows/testbot-ci.yml
  • [ ] In GitHub: Settings > Branches > Protect main > require testbot / Full test gate
  • [ ] For Netlify: configure deploy notifications or use templates/github/deploy-gate.yml
  • [ ] Add secrets to GitHub Actions: Settings > Secrets and variables > Actions

Updating testbot

cd ~/Documents/projects/testbot
# make your changes
npm install -g .           # reinstall globally

# hooks in all projects automatically use the new version
# (hooks call the global testbot binary by absolute path)