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

nlt-kit

v5.1.0

Published

Network Ledger Technology (demo server), using SNAP on top of Solid

Readme

nlt-kit based on snap-solid)

SNAP in the browser, on top of Solid.

Make sure you have Redis running. Unfortunately, you can't use nlt-kit with the domain name 'localhost', due to a restriction in the built-in identity provider. So please follow the instructions from https://stackoverflow.com/questions/7580508/getting-chrome-to-accept-self-signed-localhost-certificate (domain name: lolcathost.de) to generate the following files:

	lolcathost.de.crt
	lolcathost.de.csr
	lolcathost.de.ext
	lolcathost.de.key
	myCA.key
	myCA.pem
	myCA.srl

Now run:

npm install
npm test
npm run build
export NODE_EXTRA_CA_CERTS=myCA.pem
export DEBUG=*
export HTTPS=true
export PORT=443
export PUBLIC_PROTOCOL_SUFFIX=s
export DOMAIN=lolcathost.de
export TLS_CERT=lolcathost.de.crt
export TLS_KEY=lolcathost.de.key
npm start

Now browse to https://lolcathost.de/ (its DNS points to your machine), create a user, and log in.