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

@arnilo/prism-hooks

v0.12.1

Published

Out-of-process hooks.json adapter for Prism: Claude/Codex-compatible declarative hooks compiled onto public extension, middleware, guardrail, instruction, and stop-hook seams.

Readme

@arnilo/prism-hooks

Run a Claude Code / Codex-compatible hooks.json against Prism. The package parses the declarative config, validates it loudly, and compiles each event onto a public Prism seam — no Prism internals, no new runtime dependency, @arnilo/prism as the only peer.

bun add @arnilo/prism @arnilo/prism-hooks
import { activateKernel, createAgent, createExtensionKernel } from "@arnilo/prism";
import { createHooksExtension, hookCommandHash, parseHooksConfig } from "@arnilo/prism-hooks";

const config = parseHooksConfig(await readFile("hooks.json", "utf8"));
const handler = { type: "command", command: "node audit-tool.js" } as const;
const hooks = createHooksExtension(config, {
  trusted: { [handler.command]: hookCommandHash(handler) },
});

const kernel = createExtensionKernel();
await kernel.load([hooks]);
const activated = activateKernel(kernel);

const agent = createAgent({
  model,
  provider,
  guardrails: hooks.guardrails, // required for UserPromptSubmit / PreToolUse / PostToolUse
  instructionInjectors: activated.instructionInjectors,
  stopHooks: activated.stopHooks,
  middleware: activated.middleware,
});

Event → seam map

| hooks.json event | Prism seam | | --- | --- | | SessionStart | session_start middleware → instruction-injector context queue | | UserPromptSubmit | input guardrail (block) → instruction-injector context queue | | PreToolUse | tool_call middleware (updatedInput) + tool_input guardrail (deny) | | PostToolUse | tool_result middleware (context) + tool_output guardrail (deny) | | Stop | registered stop hook, bounded by RunLimits.maxStopContinuations |

Guardrails and stop hooks are returned/registered as inert contributions: the host activates them through AgentConfig (or RunOptions), exactly like every other kernel contribution.

Semantics

  • command handlers spawn with an argv array — the command string is tokenized locally (quotes/escapes only) and never run through a shell; "shell": true is rejected at parse time.
  • Exit codes follow Claude/Codex: 0 success (JSON stdout parsed), 2 block with stderr as the reason, anything else a non-blocking error reported as hooks:warning. There is no exit code 64 in either reference.
  • timeout is in seconds (default 600); expiry warns and never blocks.
  • Matchers: literal tokens (with |/, alternatives) select exactly; anything with metacharacters is an unanchored regex. No $1 capture substitution.
  • additionalContextLimit is a token threshold (default 2500, 0 = unlimited); oversized context spills to <tmpdir>/hook_outputs/ and a pointer is injected.
  • async: true handlers run detached; their context lands at the next assembly.
  • Trust: options.trusted maps a command string to a digest from hookCommandHash() (SHA-256 over the effective argv). Unlisted or mismatched handlers are skipped with a warning; trusted: "all" is the logged escape hatch.

Full documentation: docs/hooks.md and docs/middleware-hooks.md.