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

@verkflode/remit-claude-code

v0.4.1

Published

Remit for Claude Code: Allow/Ask/Never authority over every tool call via a PreToolUse hook, with job grants and a shared decision log.

Vulnerabilities

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

Links

Git

Maintainers

icinezaicineza

Keywords

Readme

@verkflode/remit-claude-code

Remit for Claude Code: personal agent authority — owner-set Allow / Ask / Never tiers enforced on the PreToolUse hook seam, with every decision recorded.

The tier mapping is exact: Allow → allow (no prompt), Ask → ask (Claude Code's own native approval prompt is the transport), Never → deny with a reason the model sees.

Install

npm install -g @verkflode/remit-claude-code
remit-cc init

init creates ~/.remit/ with conservative defaults and prints the hook snippet to add to your Claude Code settings (.claude/settings.json per project, or ~/.claude/settings.json for everywhere). Remit deliberately never edits settings files itself — the hook is the authority surface, so installing it is the owner's move.

Owner surface

remit-cc status                                   tiers and state paths
remit-cc grant <areas> [scope:<path>] [for:<dur>] pre-authorize a bounded batch
remit-cc grants / revoke <id|all>                 list / end grants
remit-cc cap <area> <N> per <hour|day|7d>         temporal cap (v0.4)
remit-cc cap raise <area> to <N> for <dur>        temporary, self-expiring raise
remit-cc caps                                     caps and current usage
remit-cc export --dogwood-events                  decision log as a Dogwood-replayable trace

State lives in ~/.remit/ — the machine-wide authority root shared by every Remit adapter, so a grant or cap set here binds every governed agent on the machine, and the decision log answers "what did ANY agent do today" in one place.

Seam grade and honest limitations are stated in design 0002: hooks are the outermost interception this host offers (the catalog classifies settings/hook files as change-settings, default Never, so governed tools cannot remove the hook), and ask resolutions are not reported back to hooks.

MIT © Verkflöde