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

code-handover

v1.0.0

Published

Generate a project handover markdown from static analysis and optional LLM summaries

Readme

code-handover

Generate a project handover markdown file from static analysis (structure, configs, dependencies) and optionally enrich it with LLM-written summaries of important codebase features.

Install

npm install -g code-handover

Or run without installing:

npx code-handover generate

Usage

handover generate [path] [options]

| Option | Description | Default | |--------|-------------|---------| | path | Project directory to analyze | . (current directory) | | -o, --output <file> | Output markdown file path | HANDOVER.md | | --llm | Use LLM to add "Important features" and "Conventions and gotchas" | off | | --no-llm | Disable LLM (default) | |

Examples

# Generate HANDOVER.md in current directory
handover generate

# Generate for another project
handover generate ../my-app

# Custom output file
handover generate -o docs/HANDOVER.md

# With optional LLM summaries (requires API key)
handover generate --llm -o HANDOVER.md

Optional LLM enrichment

With --llm, the tool calls an LLM to add two sections:

  • Important features – What the codebase does and main modules.
  • Conventions and gotchas – Testing style, lint rules, non-obvious pitfalls.

Set one of these environment variables (no secrets are written to the handover file):

  • OPENAI_API_KEY – uses OpenAI (e.g. gpt-4o-mini).
  • ANTHROPIC_API_KEY – uses Anthropic (e.g. claude-3-5-haiku).

If --llm is set but neither key is set, the tool skips LLM enrichment and prints a warning.

What the handover contains

The generated markdown includes:

  1. Project overview – Name, repo URL (from git), one-line description (from README or package.json).
  2. Tech stack – Languages, frameworks, key dependencies.
  3. Directory structure – High-level tree and folder notes.
  4. Entry points and scripts – Main files and npm (or similar) scripts.
  5. Environment and config – Env files, config files, referenced env var names (no values).
  6. How to run – Install, dev, test, build commands.
  7. Important features (optional, with --llm) – Bullet list from the LLM.
  8. Conventions and gotchas (optional, with --llm) – Bullet list from the LLM.

License

MIT