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

@workstarlab/release-readiness

v0.1.0

Published

A fast, dependency-free baseline readiness check for Node.js repositories.

Readme

@workstarlab/release-readiness

A fast, dependency-free baseline check for Node.js repositories. It catches missing release hygiene before a handoff or deployment: documentation, license, CI, lockfile, scripts, runtime metadata and obvious unignored environment files.

This is a deterministic preflight tool, not a security audit, compliance certification or substitute for tests and human review.

Run without installing

npx @workstarlab/release-readiness .

Use machine-readable output in CI, or fail on warnings as well as errors:

npx @workstarlab/release-readiness . --json
npx @workstarlab/release-readiness . --strict

Library

import { inspectRepository } from "@workstarlab/release-readiness";

const report = await inspectRepository(process.cwd());
if (!report.ready) {
  console.error(report.checks.filter((check) => check.status === "fail"));
}

The CLI exits with status 1 when required checks fail. --strict also treats warnings as a failing result.

What it checks

  • valid package.json and common package metadata;
  • repeatable build, test, type/static-check and lint/format scripts;
  • README, license, security policy and dependency lockfile;
  • a GitHub Actions workflow and .gitignore;
  • obvious .env variants that exist without an explicit ignore rule.

The environment-file check is intentionally narrow and never reads or prints secret values.

Development

npm install
npm run verify

Requires Node.js 20 or newer. Licensed under MIT.