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

huntbook

v0.1.0

Published

Executable playbook for your bug bounty ops - pipeline, intel, dedup and reports as plain files an AI session can drive.

Vulnerabilities

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

Links

Git

Maintainers

zuoqingzuoqing

Keywords

bug-bountysecurityclipipelinereconagentplaybook

Readme

huntbook

test npm license

Executable playbook for your bounty ops. Pipeline, intel, dedup and reports as plain markdown — a workspace an AI session can drive as well as you.

Most recon tools want to run your life from a server: a database here, a docker stack there, a dashboard nobody opens twice. huntbook is the opposite — your entire bounty operation lives in one .huntbook/ folder of markdown files. git init it, sync it, let an AI coding session drive it. Clone anywhere, and the whole war room is back.

npx huntbook init    # one folder, zero services
huntbook add --target acme.com --title "Login rate limit bypass" --severity high --grade A
huntbook next        # claims the highest-priority case — or holds your current one
huntbook report 2026-08-28-acme-com-login-rate-limit-bypass   # platform-ready markdown

What v0.1 does

  • pipeline — a case state machine over plain files: todo → doing → done → submitted, priority = grade (A-E) first, then severity, and a 90-minute claim window so two agent sessions (or you + an agent) never fight over the same target mid-audit. Expired claims re-enter the queue automatically; nothing is ever lost, it is all just files.
  • report — renders a case into a platform-ready markdown report: severity banner, target header, and the evidence trio (steps / impact / evidence).

Why files, not a platform

| lane | tools | what's missing | | --- | --- | --- | | recon engines | bbrf · reNgine · Osmedeus · ScopeSentry | all need a server/db/docker stack | | vuln management | Faraday · DefectDojo · Dradis | team-grade platforms, pentest-report shaped | | single-point extractors | mapxtractor · jsmap · sourcemapper | pure recon, no workflow |

huntbook's lane: a solo hunter (or an AI session) wants a desk, not a datacenter. Every command outputs structured markdown — idempotent, no TTY required, safe to paste straight into the next prompt.

Roadmap

v0.2 intel — per-target intelligence briefs aggregated from NVD/GHSA/changelogs · v0.3 dedup — three-state submission triage (original / duplicate / unsure) against your own history.

Design notes

The workflow encodes six months of real bounty operations practice. v0.1 ships the production-proven spine only; scope decisions and the competitive gap analysis are in DESIGN.md.

Development

pnpm install
pnpm test          # vitest suite
pnpm lint          # oxlint + oxfmt
pnpm build         # tsdown

MIT © lvyanyan