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

@tinoy/pi-io-guard

v0.2.0

Published

Write coordination for one shared tree: per-worker path claims, locks, version checks and the io_status tool.

Downloads

375

Readme

[!WARNING] Do not install anything here yet.

This is a fast-moving prototype: the interfaces change without notice, and nothing here is stable. Every package in this project is headed for a stable 1.0, but that is still some way off. Install one only if you intend to follow the code and expect breakage.

@tinoy/pi-io-guard

Write coordination for a crew of sessions sharing one tree. The worker side runs hooks only: it records what this worker read and guards what it writes. The foreman side is a single tool, io_status, for inspection and the atomic reclaim of a claim.

pi install npm:@tinoy/pi-io-guard

What it needs at call time

A writable store directory — ~/.local/pi/foreman/io under the home directory, holding the per-worker claim records, the per-write locks, the parked proposals and the version stamps. The guard fails closed: an unreadable claim, an untrusted or missing version record, or a guard error all refuse the write rather than allow it.

A package with no fleet in the session still loads: io_status answers for whatever claim records are on disk, and the write guard simply has nothing to allow.

Registers

io_status.

Works better with

| Neighbour | You gain | You lose without it | Install | | --- | --- | --- | --- | | @tinoy/pi-fleet | a dispatcher that hires workers against these claims and reclaims them on retirement | the records are written and read by hand, and nothing turns a reclaim into a new hire | pi install npm:@tinoy/pi-fleet |

Dependencies

pi-supplied imports (@earendil-works/pi-coding-agent, typebox) are peers with a * range. Plain dependency: @tinoy/pi-ext-lib, whose globOverlap decides what "this path is inside that claim" means, so the guard and the dispatcher cannot disagree about a glob.

Licence

MIT — see the repository LICENSE.