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

tupelo-lite

v0.0.17

Published

Immutable data store with digital signatures

Readme

Tupelo: Leaf

Tupelo: Leaf is an immutable datastore built for cloud-native, serverless application development. Leaf works for both simple, rapid application development and high security, high compliance environments.

Leaf is a new kind of database built specifically for cross-organization, cross-application and compliance use-cases. Using Leaf is relatively simple and scales out both in terms of dev complexity and transactions per second.

Leaf is built to take advantage of modern cloud environments from AWS to Kubernetes. Leaf requires three pieces of infrastructure: a message queue (MQTT), a key/value store (eg DynamoDB or TiKV), and a function runner to expose an API (lambda, azure functions, OpenFAAS).

The underlying datastructure allows the system to scale easily from 0 all the way up to 1000s of transactions per second with little or no work from the dev or ops teams.

Deploy

Deploy to any major cloud system or kubernetes is as simple as sls deploy. More details here: (link)

What is it?

Leaf is an immutable object store. Objects are trees of data with owners. Owners are allowed to write to the object. Policies are attached to objects and they allow read/write capabilities as necessary for an application. Policies are written in Rego from OpenPolicy Agent, an industry standard langauge used extensively in Kubernetes.

Leaf has a Javascript (TypeScript) and Go api. Usage from the client side is also simple:

const identity = new Identity("did:tupelo:123", privateKey)
const client = new Client("https://myapi-endpoint.com", {defaultIdentity: identity})

const myCoolObj = client.newTree()
myCoolObj.set("/path/to/your/value", "myValue")

assert.Equal("myValue", myCoolObj.get("/path/to/your/value")) // true

Realtime

Every Leaf deploy has a message queue associated and publishes update to objects. This means that you can stay up to date as objects change. The underlying connections and updates are handled automatically for you.

const identity = new Identity("did:tupelo:123", privateKey)
const identity2 = new Identity("did:tupelo:456", privateKey2)

const client = new Client("https://myapi-endpoint.com", {defaultIdentity: identity})
const client2 = new Client("https://myapi-endpoint.com", {defaultIdentity: identity2})

const myCoolObj = client.newTree()
const did = myCoolObj.did()
myCoolObj.set("/path/to/your/value", "myValue")

otherClientTree = client2.getLatest(did)
assert.Equal("myValue", otherClientTree.get("/path/to/your/value")) // true

otherClientTree.subscribe()

myCoolObj.set("/path/to/your/value", "new value")

// the other client is notified via a queue
assert.Equal("new value", otherClientTree.get("/path/to/your/value")) // true