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

@flowrail/hook

v0.0.5

Published

FlowRail PreToolUse hook dispatcher for Claude Code (POC). Pre-write secret scan + LLM-backed code verifier; pre-bash supply-chain check via the FlowRail MCP server.

Downloads

573

Readme

@flowrail/hook

PreToolUse hook dispatcher invoked by Claude Code on every Write/Edit/MultiEdit and Bash call. Exposes two sub-commands:

  • flowrail-hook pre-write — reconstructs post-edit content (handles plain Write, Edit with replace_all: false / true, and MultiEdit composition), runs a regex secret scan, and routes code files through the FlowRail server's MCP flowrail_verify_code tool against the active design review's guardrails.
  • flowrail-hook pre-bash — inspects tool_input.command, runs npm install --dry-run to resolve the tree on package-install patterns, and routes through MCP flowrail_check_dep_install for the 4-signal supply-chain check.

Reads FLOWRAIL_MCP_URL (default http://localhost:8787) for the server base URL and FLOWRAIL_API_KEY for the bearer. The full install (@flowrail/init-poc) bakes the URL into the hook command line in .claude/settings.json (tracked, no credential), but it does NOT bake the bearer there — .claude/settings.json is committed, and the env-reference contract requires the API key to live only in the tester's shell env. The hook inherits FLOWRAIL_API_KEY from whatever shell launched Claude Code; if that shell didn't export it, MCP calls fail open against the local-dev fallback. Keep FLOWRAIL_API_KEY exported (e.g. via ~/.zshrc) so every Claude Code session inherits it.

You probably don't invoke this directly@flowrail/init-poc writes the right .claude/settings.json entries for you.

Source + docs: https://github.com/anshumanbh/flowstate

POC, eval-only.