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

ci-debug

v0.1.0

Published

Safely debug CI environments. Prints system info and environment variables (with secrets redacted).

Downloads

92

Readme

ci-debug

Safely print system info and environment variables for debugging CI pipelines.

The Problem: When CI fails, you need to know the environment state (Node version, OS, specific env vars). Running printenv is dangerous because it leaks API keys and secrets into public logs.

The Solution: ci-debug prints a beautiful summary of the system and lists environment variables, automatically redacting any keys that look like secrets (e.g., API_KEY, GITHUB_TOKEN, PASSWORD).

Install

npm install ci-debug

Usage

CLI (Recommended)

Add this step to your GitHub Actions or CI pipeline when things go wrong:

- run: npx ci-debug

Output Example:

🔍 CI Debug Info v0.1.0
----------------------------------------
📦 System
  OS:       Linux 5.15.0-1048-azure (linux)
  Arch:     x64
  Node:     v20.9.0
  CPUs:     2
  Memory:   7000 MB Total

📂 Context
  CWD:      /home/runner/work/project/project

🔑 Environment Variables
  CI: true
  DATABASE_URL: ***** [REDACTED] *****
  GITHUB_TOKEN: ***** [REDACTED] *****
  NODE_ENV: production
  npm_package_version: 1.0.0
----------------------------------------

API

import { getDebugInfo } from 'ci-debug';

const info = getDebugInfo();
console.log(JSON.stringify(info, null, 2));

Security

This tool uses a regex heuristic to detect keys containing: key, secret, token, password, auth, credential, private, cert, sig.

These values are replaced with [REDACTED].

License

MIT

{ github.com/mgks }

Website Badge Sponsor Badge