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

offset-log

v0.0.0

Published

experiment for a immutable database.

Readme

offset-log

experiment for a immutable database.

Idea

this is an experiment to see how simple a database can be. this is strictly an append-only, buffers are written to the database, with a light framing (the length of that buffer) and the offset is returned as a key.

Using the offset as the key gives you a very small key that increases monotonically. an 8 byte key can represent a 256 terabyte database. The key smallness also means that indexes can be very small.

Since the database does very little, it can also be very fast. Since the keys are small, that simplifies the indexes too.

I am writing this to experiment with indexes that are simply a list of keys with a particular sort applied to them - just enough to enable binary search.

API ideas

there are lots of ways you could implement a frame around the data, which might have different benefits. you could use json or csv format, and then you could view the database in a text editor.

you could encrypt the data, with authentication so that you can detect interference.

what should the api for framing look like? given an offset, you need to be able to get the next, and the previous

License

MIT