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

sopa

v0.1.6

Published

Local package manager for web

Readme

#Sopa

Sopa is a local package manager. You can imagine it was a local version of bower.

##Getting Start

###Install

$ npm install sopa -g

###Pull package To use sopa, the first thing you need to do is setting the components dir use set-dir:

$ sopa set-dir ~/sopa_components

The dir is a place where store all your packages pull from web.

Now I pull the jQuery from cdnjs (https://cdnjs.com/), for example.

Firstly I search jQuery on cdnjs and copy the static file url. Here I found is a version of 2.1.3 js file - //cdnjs.cloudflare.com/ajax/libs/jquery/2.1.3/jquery.min.js

So I need to pull this file:

$ sopa pull [email protected]@js //cdnjs.cloudflare.com/ajax/libs/jquery/2.1.3/jquery.min.js

jquery is the package name you defined and 2.1.3 is the version of the package. Note that you are required a file type ( js or *css ).

###Install package Now I need to install jQuery which I'd pulled from cdnjs at current folder.

$ sopa install [email protected]@js javascripts

The last command is the folder you wanna install the static file into.

###List Sometimes you may wanna list what packages you had pull or what version you'd pull. Sopa has a command help you list it:

$ sopa ls
vue
jquery

If you wanna show what jQuery version you'd pulled, you can:

$ sopa ls jquery
1.11.2
2.1.3

##Why The reason why I create Sopa is my college always limit my data whithin 9 GB per month. Everytime I bower install or npm install cost much data. So I made Sopa.

##Sopa It named Sopa, in memory of my idol Aaron Swartz, who againsted SOPA.