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

@keicoin/work

v0.4.2

Published

Proof-of-work for Kei blocks: difficulty tiers, local generation, work-server client.

Readme

@keicoin/work

Proof-of-work for Kei blocks: difficulty tiers, local generation, work-server client.

Run the server beside a node:

KEI_NODE_URL=http://127.0.0.1:7076 PORT=7077 kei-work-server

Set WORK_SERVER_TOKEN to require Authorization: Bearer …. Clients point workServer at the printed URL; requests use the same work_generate JSON API in local, test, and production deployments.

The token belongs in a header, not in the URL — a URL is what an error message names, and a header is not:

const kei = await Kei.start({
  workServer: { url: 'https://work.example/', headers: { authorization: `Bearer ${token}` } },
})

Part of kei-transaction — real currencies and items for browser games. Install kei-transaction instead unless you are counting bytes; these sub-packages exist for bundle size, not as a puzzle you have to solve.

bun add @keicoin/work     # or npm / pnpm / yarn

What is in here

Anti-spam without fees. Difficulty is tiered by how attractive an operation is to abuse:

| Tier | Operations | |---|---| | A (highest) | issue, mint, commit, commit_close | | B (standard) | send, transfer, swap legs | | C (cheap) | receive, claim, burn |

claim is deliberately cheap: a thousand players claiming at once must not produce a visible pause.

Status

M4 of eleven. Native item and rooted-claim wire layouts now match the node, and the authenticated work server is runnable. The public API defaults to the real node at https://testnet.keicoin.org/rpc; MockNode remains the hermetic reference implementation for claim flows until the M4 RPC surface is deployed. The testnet is one best-effort node with weak consensus and nothing there holds value.

See the full documentation.

MIT.