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

open-on-npm

v1.0.2

Published

Open npm packages on the npmjs.com registry

Vulnerabilities

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

Links

Git

Maintainers

abranheabranhe

Keywords

npmopen-on-npmopenpackagenpm-package

Readme

Sometimes you want to open an npm packages on the registry after published, or at any time. This pretty 🖖 simple cli tool will help you with that!

See

Install

$ npm install open-on-npm

CLI

Open npm packages on the npmjs.com registry

Usage

  $ open-on-npm [package-name/null]

Options

  -f, --feedback  Send a feedback
  -h, --help      Show help message and close
  -v, --version   View package Version
	  --force     Open the package url even if it is not published

Examples

  $ open-on-npm non-published-packge
  The packge 'non-published-package' is not published. Try --force!

  $ open-on-npm non-published-packge --force

  $ open-on-npm

Related

  • openup: Open repositories from your terminal on your web browser.

Team

|Carlos Abraham Logo| | :-: | | Carlos Abraham |

License

MIT License © Carlos Abraham