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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@bleenco/morose

v0.3.0

Published

lightweigth alternative to npm registry

Readme

morose

Run npm registry on your own servers.

morose is currently in development mode. It currently supports:

  • registering/uploading packages
  • supports basic semver wildcards (1.1.x) and ranges
  • a few basic routes to see what's registered
  • all packages info is saved in cache

Here's what it doesn't do yet:

  • authentication on publish
  • searching for packages

Installation

$ npm install morose -g

Usage

Running a Server

morose-server

Publishing package to registry

cd into package root directory you want to publish (should have package.json file) and:

morose publish [url:port]

where url is the HTTP url where morose-server is running. ie:

morose publish https://morose.example.com:4720

you can ofc omit port if morose server is running on port 80.

Installing package from morose server

npm install https://morose.example.com:4720/package/[package-name]/latest

or

npm install https://morose.example.com:4720/package/[package-name]/1.1.0

LICENCE

MIT