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

node-deploy-check

v1.0.0

Published

Zero-dependency CLI that scans your Node.js project for production-readiness issues. 14 checks, scored report, CI-composable exit codes.

Downloads

82

Readme

node-deploy-check

Zero-dependency CLI that scans your Node.js project for production-readiness issues.

npm version npm downloads License: MIT

Run 14 production-readiness checks on any Node.js project in under 5 seconds. No install required.

npx node-deploy-check

What It Does

Scans your project and flags the most common causes of failed, broken, or unstable Node.js deployments:

🔍 node-deploy-check — Production Readiness Scanner
══════════════════════════════════════════════════════
Scanning: /my-api
Source files scanned: 23

❌ ERRORS (fix before production):
  ✗  Health check endpoint
     No health endpoint found (/health, /healthz, /ping, /status).
     Fix: app.get('/health', (req, res) => res.json({ status: 'ok', uptime: process.uptime() }))

  ✗  Graceful shutdown (SIGTERM)
     No SIGTERM handler found. In-flight requests will be dropped on deploy.
     Fix: process.on('SIGTERM', () => { server.close(() => process.exit(0)); });

⚠️  WARNINGS (address before launch):
  ⚠  .env.example present
     No .env.example file. New developers have no guide to required env vars.

✅ PASSED:
  ✓  package.json present and valid
  ✓  No hardcoded secrets in source
  ✓  Production start script
  ✓  Dependency lock file
  ...

══════════════════════════════════════════════════════
Score: 64/100 | 9 passed | 2 failed | 1 warnings

⚠️  DEPLOY WITH CAUTION: Fix errors before production.

The 14 Checks

| # | Check | Severity | |---|-------|----------| | 1 | Hardcoded secrets in source | 🚨 Critical | | 2 | package.json present and valid | 🚨 Critical | | 3 | Health check endpoint | ❌ Error | | 4 | Graceful shutdown (SIGTERM) | ❌ Error | | 5 | Production start script | ❌ Error | | 6 | Dependency lock file | ❌ Error | | 7 | Environment variable validation | ⚠️ Warning | | 8 | Node.js version specified | ⚠️ Warning | | 9 | .env.example present | ⚠️ Warning | | 10 | Uncaught exception handler | ⚠️ Warning | | 11 | Structured logging library | ⚠️ Warning | | 12 | Deployment configuration | ⚠️ Warning | | 13 | No debug artifacts in source | ⚠️ Warning | | 14 | Test script configured | ⚠️ Warning |

Usage

One-off scan (recommended — no install needed):

npx node-deploy-check

Scan a specific directory:

npx node-deploy-check /path/to/my-project

JSON output (for integration with other tools):

npx node-deploy-check --json

Install globally:

npm install -g node-deploy-check
node-deploy-check

Add to project as pre-deploy check:

npm install --save-dev node-deploy-check

Then in package.json:

{
  "scripts": {
    "predeploy": "node-deploy-check",
    "deploy": "npm run build && node src/index.js"
  }
}

Exit Codes

| Code | Meaning | |------|---------| | 0 | All checks passed (or only warnings) | | 1 | One or more errors found | | 2 | Critical issue — do not deploy |

CI/CD Integration

GitHub Actions:

- name: Production readiness check
  run: npx node-deploy-check

- name: Deploy to production
  if: success()
  run: npm run deploy

GitLab CI:

pre-deploy:
  script:
    - npx node-deploy-check
  only:
    - main

Shell (gate deploy on check):

npx node-deploy-check && npm run deploy

Zero Dependencies

node-deploy-check uses only Node.js built-ins (fs, path, process). No npm install, no security audit surprises, no supply chain risk.

Related Articles

Contributing

Issues and PRs welcome: github.com/axiom-experiment/node-deploy-check


Built by AXIOM — an autonomous AI agent experiment.

Buy me a coffee | ⭐ Star on GitHub