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

@forestrie/mandate-register

v0.2.4

Published

Bundled mandate-register CLI for cross-repo system tests (ARC-0024)

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

forester-robinforester-robin

Keywords

Readme

@forestrie/mandate-register

Bundled mandate-register CLI (ARC-0024): Univocity instance provisioning, onboarding, and BYOK custody-mode operations. Published to public npmjs with SLSA provenance (FOR-360) — no registry token, no GitHub account, no relationship with the mandate operator is required to install or run it.

That is the point: the exit paths documented in FORKING.md and ADR-0005 are only credible if a forker can drive them with tooling the operator cannot gate. This package is that tooling.

Usage (tokenless)

npx @forestrie/mandate-register            # list subcommands
npx @forestrie/mandate-register provision --mode B ...
npx @forestrie/mandate-register onboard request ...

Subcommands:

| Command | Purpose | | --------------------------------------- | --------------------------------------------------------- | | onboard request / status / redeem | Self-service onboard token flow (FOR-173) | | provision | Full genesis + descriptor emission (FOR-100) | | privy onboard-mode-c | Mode C Privy wallet onboarding (FOR-112) | | privy revoke-mode-c | Mode C kill switch — remove mandate as signer (FOR-114) | | privy describe-post-revoke-actions | Post-revoke KEY_DIRECTORY checklist (FOR-131) | | privy exit-to-mode-b | Repoint agent signing to a user-operated signer (FOR-311) |

Exiting to Mode B

The Mode C→B exit (ADR-0005 operational appendix, FORKING.md §5b) runs entirely through this CLI:

# step 2 — revoke mandate's signer access on the user-owned wallet
npx @forestrie/mandate-register privy revoke-mode-c \
  --wallet-id <id> --mandate-signer-id <quorum-id> ...

# step 3 — repoint the deployed agent at a user-operated signer
npx @forestrie/mandate-register privy exit-to-mode-b \
  --log-id <32-hex> --signer-url https://<your-signer>/v1/sign ...

publicRoot is unchanged by the exit (ARC-0022 I5): the same key keeps signing under a new operator with no re-registration.

Development

Build bundles @mandate/register + @mandate/privy-admin with esbuild:

pnpm --filter @forestrie/mandate-register build
pnpm --filter @forestrie/mandate-register test

Releasing

Tag mandate-register-v<version> (matching package.json) on main; publish-mandate-register.yml publishes to npmjs via OIDC trusted publishing in the npm-publish environment. Cross-repo consumers (e.g. forestrie/system-testing) install via their manifest kits pins.