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

ipfs-twitter-resolver

v0.0.1

Published

tiny server to resolve and redirect /twitter/user/key addresses to IPFS hashes

Readme

ipfs-twitter-resolver

tiny CLI server for resolving /twitter/user/key to an IPFS address

background

IPFS has a name resolution mechanism called IPNS, which will resolve addresses of the form /ipns/Qmfoobarbaz to an IPFS address, where Qmfoobarbaz is the multihash of a public key. These are generally resolved using a DHT. DHTs have many great properties, but long-term survivability is not one of them.

How swell would it be if you could make a tweet on Twitter like

blog = /ipfs/QmeV1kwh3333bsnT6YRfdCRrSgUPngKmAhhTa4RrqYPbKT

then hit a normal HTTP server on the URL http://example.com/twitter/noffle/blog to get redirected to that IPFS address? This is a pretty easy way to update the hash that say, a blog, points to.

example

$ npm install -g ipfs-twitter-resolver

$ ipfs-twitter-resolver &

$ curl -L http://localhost:8000/twitter/noffle/avatar
...
< HTTP/1.1 302 Found
< Location: https://ipfs.io/ipfs/QmdXZsi5GvsnKewXK35DypLxTzseR8tuVGyBLMQcBpEmMc/avatar.png
<

install

With npm installed, run

$ npm install -g ipfs-twitter-resolver

license

ISC