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

@projectpac/negotiation

v0.6.0

Published

Part of PAC: @projectpac/negotiation.

Readme

@projectpac/negotiation

The negotiation engine: the suggest-and-agree rounds that joint-search, objects, and meta each used to carry a copy of, offered to flows as one service.

A factory rather than an actor. A flow hands over a spec -- its record accessors, its choices, its messages -- and drives what comes back with its own hands: every apply, ask, run, and artifact call goes through closures over the flow's own context, so attribution, policy, and inject gates are exactly what they were when the flows inlined these steps. The engine itself reaches nothing, which is why it injects nothing and runs on any node however bare.

ctx.negotiation.rounds (createRounds): propose and review revisions of a shared artifact until both sides mark one agreed, within a bounded number of rounds. The flow supplies what to draft and how to judge; the engine supplies the round discipline.

Each round drafts in a workspace of the artifact store, and the store caps how many one flow holds open. So the engine closes each workspace the moment its round is over -- after the commit, on an agreement -- and a flow that gives a record up mid-round calls abandon(id) to close the one that round left behind. Before this, a node stopped negotiating after eight tasks: the cap had filled with finished rounds' leavings, and every open after that was refused until the store's TTL expired them an hour later.

What happens to an agreement afterwards is a separate choice, and not this package's: @projectpac/jc-box-run carries one out in a box, and meta installs what it agreed as a plugin on both nodes instead.