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

@sidestr/wallet

v0.0.7

Published

the sidestr wallet library (wallet.mjs, no DOM) and page

Readme

sidestr wallet

A wallet for a sidestr chain that needs nothing of the chain's producer: it reads and validates the chain from a mirror (the same chain.json, blocks.json, blocks.dat the explorer uses), keeps your key in the browser, signs spends in the page, and sends them to a Nostr relay as kind 23500 events, where the producer picks them up. SPEC section 11.

Open index.html?chain=<chain id> (the wallet asks the relays for the signer's tip announcement, which names the mirrors, and takes the one whose chain.json names the announcer as signer) or index.html?mirror=<mirror URL>. It follows the announcements live, so a new block shows within seconds, and it marks the mirror ✓ or ⚠ against the signer's announced tip. The engine and libraries load from pinned commits on jsdelivr; ?lib=, ?cdn= and ?explorer= override them for development.

wallet.mjs is the logic with no DOM, so node test/wallet-test.mjs --mirror <URL> (or --chain <id>) exercises it against a live chain: identity, coins and maturity, a real signed spend checked with the curve's verifier, codec round-trip, address handling; --send publishes it and waits for the mirror. Keys are stored unencrypted in the browser, as the BLAKE wallet does: small amounts.

Signing with a browser signer

With an extension that offers window.nostr.sidestr (proposals/browser-signer.md; Podkey is the reference), the page offers "use my extension's key": it stores only the public key, builds each spend unsigned (build({ pub, ... }), same layout and fee as a signed one), and signWith(browserSigner(), built) hands it to the extension, which resolves the chain itself, shows the spend in its own window and signs only its own coins. The answer is held to the txid that was built and to a validator's check of every signature before it is published, from a throwaway event key as always. The EVM, peg-ins and the desk sign other things (an Ethereum transaction, a parent transaction) and still need the key in the page. node test/signer-test.mjs checks the round trip against a stand-in signer.