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

fossilize-cli

v0.1.0

Published

Generate documentation from actual code execution evidence — test-driven docs that never lie.

Readme

fossilize-cli

Generate documentation from actual code execution evidence — test-driven docs that never lie.

The Problem

Documentation is usually broken in one of three ways:

  1. Manual and stale — engineers ship code faster than they update docs
  2. Auto-generated but shallow — signatures and comments, not real behavior
  3. AI-generated but ungrounded — sounds polished, fabricates examples

The Solution

Fossilize generates docs from evidence:

  • Test descriptions become behavior documentation
  • Export signatures become API references
  • Route handlers become API docs (with real status codes from tests)
  • Import graphs become architecture docs
  • Git history becomes changelogs

Every example is REAL — from test execution, code signatures, or git history. Never fabricated.

Installation

npm install -g fossilize-cli

Usage

# Generate all docs for current project
fossilize .

# Output to specific directory
fossilize . --output docs/

# Only generate README
fossilize . --readme-only

# Output doc structure as JSON
fossilize . --format json

# Show what would be generated (no files written)
fossilize . --dry-run

# Skip test execution
fossilize . --skip-tests

# Skip git analysis
fossilize . --skip-git

What Gets Generated

| Document | Source | |----------|--------| | README.md | package.json + exports + test summary | | docs/api.md | Route handlers + test-verified status codes | | docs/architecture.md | Import graph + directory structure | | docs/changelog.md | Git history with conventional commit grouping |

Supported Stacks

  • Languages: TypeScript, JavaScript (Python/Rust/Go detection planned)
  • Frameworks: Next.js (App Router), Express, Fastify, Hono
  • Test Runners: Vitest, Jest, Mocha (pytest/cargo test detection planned)

Key Principle

If no test exists for a function, Fossilize documents the signature but notes "no test coverage." It will never fabricate examples. Trust comes from proof.

License

MIT