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

should-i-ship

v0.1.11

Published

Local launch-readiness scanner for AI-built apps.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

zerotobuildzerotobuild

Keywords

Readme

Should I Ship CLI

Run a local launch-readiness scan before you put real users on an AI-built app.

npx should-i-ship@latest scan

The scan writes:

.should-i-ship/report.md
.should-i-ship/findings.json

The free report shows the top 3 prioritized findings with full detail. Additional findings are listed by category and severity only.

Source code is not uploaded. In git repos, Should I Ship scans git-visible files, including uncommitted files that are not ignored by .gitignore.

Create an unlock link without prompting:

npx should-i-ship@latest scan --unlock-link

Skip unlock-link upload entirely:

npx should-i-ship@latest scan --no-upload

Unlock links upload findings and scan metadata only. Source code, file contents, environment variables, and ignored files are not uploaded.

Local scans are free. Create a $10 unlock link when you want every finding unlocked with exact issue details, fixes, AI repair prompts, and a shareable web report:

npx should-i-ship@latest scan --unlock-link

Optional deeper engines are supported when installed locally. Install Semgrep with brew install semgrep and OSV with brew install osv-scanner for deeper security and dependency checks.

This is an automated launch-readiness scan, not a professional security audit.