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

hellopay

v0.1.6

Published

A fake CLI for practising releases

Downloads

294

Readme

hellopay

A fake CLI for practising releases. Not a real product.

Install

npm install --save-dev [email protected]
npx hellopay version

Always pin the version. hellopay@latest and a bare npx hellopay resolve to whatever is current at that moment, which is the opposite of what a lockfile is for.

In CI, install from the lockfile and leave install scripts off:

npm ci --ignore-scripts
npx hellopay version

This package ships no install scripts at all, so --ignore-scripts costs you nothing here — and it keeps the flag meaningful for every other dependency in your tree.

How it works

hellopay contains no binary. It declares six optional dependencies — one per platform — and npm installs only the one that matches your machine:

| Platform | Package | |---|---| | macOS Intel | @hellopay/cli-darwin-x64 | | macOS Apple silicon | @hellopay/cli-darwin-arm64 | | Linux x86-64 | @hellopay/cli-linux-x64 | | Linux arm64 | @hellopay/cli-linux-arm64 | | Windows x86-64 | @hellopay/cli-win32-x64 | | Windows arm64 | @hellopay/cli-win32-arm64 |

Before running the binary, hellopay checks its SHA-256 against a table built into this package and refuses to run on a mismatch.

Verifying where this package came from

Two steps. There is no badge to trust instead.

npm audit signatures
npm view hellopay repository.url

The second command must print github.com/hoanghuydev/hellopay. "Has provenance" only means some repository built it — anyone who takes over a package name can publish with full provenance from their own repository, and the check still passes. The repository name is the part that carries the meaning.

Known limitations of this channel

  • No shell completions. They need an install script, and this package deliberately has none. Use the shell installer or Homebrew if you want them.
  • Weaker verification than the shell installer. install.sh checks a cosign signature over checksums.txt. npm has no equivalent at install time. See HUONG-DAN-PHAT-HANH-CLI.md §5.9.4.
  • --no-optional / --omit=optional breaks it. The binary lives in an optional dependency; skipping those skips the binary. The error message tells you so.

Other ways to install

https://github.com/hoanghuydev/hellopay

MIT