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

@cero-base/cero

v2.4.0

Published

The ideal p2p API — everything is a handle, handles contain refs, refs contain rows.

Readme

@cero-base/cero

[!IMPORTANT] This project is experimental. The API is subject to change and may break at any time.

Describe your data. Cero stores it on the device, syncs it across your devices and shares it with the people you invite. No server.

Cero is the SDK apps use, one of the two Cero Base packages, on the Pear stack by Holepunch. The other, Core (@cero-base/core), holds the primitives Cero is built from.

npm install @cero-base/cero

A Cero app is three files.

// schema.js
import { cero, t } from '@cero-base/cero'

export const schema = cero.schema({
  notes: t.collection({ title: t.string, body: t.string }),
  room: { messages: t.collection({ text: t.string }) }
})
// build.js, run once and after every schema change
import { build } from '@cero-base/cero/build'
import { schema } from './schema.js'

await build('./spec', schema)
// index.js
import { cero } from '@cero-base/cero'
import { spec } from './spec/index.js'

const me = await cero('./data', spec)
await cero.put(me.notes, { title: 'first', body: 'hello' })

const room = await cero.open(me.room, { name: 'general' })
console.log(await cero.invite(room)) // give this to a friend

Your friend, on their own machine, with the same three files:

// index.js
import { cero } from '@cero-base/cero'
import { spec } from './spec/index.js'

const me = await cero('./data', spec)
const invite = '…' // the string you gave them
const room = await cero.open(me.room, { invite })
for await (const { data } of cero.watch(room.messages)) console.log(data)

That is a working, encrypted, offline-first, peer-to-peer app. Your phrase, await cero.phrase(me), opens the same identity on any other device.

Docs

Exports

| Subpath | What it gives you | | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | | @cero-base/cero | cero, t, schema, restore, peek, the 24 operators, Handle, Ref, Local | | @cero-base/cero/build | build(specDir, schema, opts) | | @cero-base/cero/server | serve(ipc, spec, opts) and Server, the worker that owns the data | | @cero-base/cero/client | cero(ipc, spec) (also connect), Client, restore, t, schema and every operator but before, after and tx, for a UI process | | @cero-base/cero/extensions | profileSync, handleSync, bundled, extensionsOf, and a light cero with t, schema and the operators, for extension modules |

The 24 operators, each also on the facade as cero.put and so on: put, set, get, del, watch, call, open, tx, invite, revoke, rotate, accept, deny, leave, close, cancel, suspend, resume, activate, deactivate, phrase, nearby, before, after.

Built on the Pear stack: Hypercore, Autobee, HyperDB, Hyperblobs, Hyperswarm, blind-peering and Bare. Runs on Node and Bare, with TypeScript declarations.

License

Apache-2.0