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

safelaunch

v1.0.12

Published

Backend Reliability Infrastructure - catch what breaks production before it breaks

Downloads

934

Readme

safelaunch

Catch what breaks production before it breaks.

safelaunch is a comprehensive environment validator for JavaScript projects. Run it before every push to catch everything that will break production.

Works with Node.js, Next.js, Vite, and Create React App projects. Automatically detects your project type and runs the right checks.

Install

npm install -g safelaunch

Two commands. That is it.

Step 1: Generate your environment manifest

safelaunch init

Scans your entire codebase, finds every environment variable your app uses, and generates env.manifest.json automatically. Works with process.env and import.meta.env.

Step 2: Validate before every push

safelaunch validate

Auto-validate on every push (Git Hook)

Install the hook once and safelaunch validate runs automatically before every git push:

safelaunch hook install

If validation fails the push is blocked until you fix the issues. Never accidentally push a broken environment again.

To remove the hook:

safelaunch hook uninstall

What safelaunch checks

safelaunch validate runs 11 checks:

  1. Missing required environment variables
  2. Empty required environment variables
  3. Runtime version mismatch (Node version)
  4. Duplicate variables in .env
  5. Dependencies not installed
  6. Dependency drift (in package.json but not installed)
  7. Variables in .env.example but missing from .env
  8. VITE_ prefix warning (Vite projects — variables without VITE_ won't be exposed to the client)
  9. REACT_APP_ prefix warning (CRA projects — variables without REACT_APP_ won't be exposed to the client)
  10. NEXT_PUBLIC_ prefix awareness (Next.js — flags variables intended for the client)
  11. .env file priority conflicts (Next.js — warns when .env.local overrides .env silently)

Example output

Running safelaunch...

project type: Next.js

⚠️ RUNTIME MISMATCH

Node required: 18 Node actual: 20

⚠️ DEPENDENCY DRIFT (1 found)

express in package.json but not installed

⚠️ ENV FILE PRIORITY (1 found)

DATABASE_URL in both .env and .env.local (.env.local takes priority)

❌ EMPTY VARIABLES (1 found)

DATABASE_URL required but empty in .env

❌ MISSING VARIABLES (1 found)

REDIS_URL required but missing from .env

✅ PASSING (1)

API_KEY present

Your environment is not ready for production.

Supported project types

safelaunch automatically detects your project type.

  • Node.js scans process.env
  • Next.js scans process.env, checks NEXT_PUBLIC_ and .env priority
  • Vite scans import.meta.env, checks VITE_ prefix
  • React CRA scans process.env, checks REACT_APP_ prefix

CI Integration

Add this to your GitHub Actions workflow:

  • name: Install safelaunch run: npm install -g safelaunch
  • name: Validate environment run: safelaunch validate

Blocks deployments automatically if any check fails.

Built by Orches

Deployment Reliability Infrastructure.

GitHub: https://github.com/karthicedric7-cloud/safelaunch VS Code: https://marketplace.visualstudio.com/items?itemName=Orches.deploycheck-vscode