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

flowmap-scan

v0.0.1

Published

Scan a TypeScript/JavaScript codebase into an architecture map — `npx flowmap-scan ./src`.

Readme

flowmap-scan

Scan a TypeScript/JavaScript codebase into a Flowmap architecture map — endpoints, call graph, databases — and publish it to your Flowmap project.

npx flowmap-scan ./src

Produces .flowmap/state.yaml. Signed in, it also fills in missing function descriptions with AI and publishes the map to flow-map.link, where your whole team's AIs read and enrich the same shared context over MCP.

Without a login it still works — you get the structural scan as a local .flowmap/state.yaml, which you can drag into your project on the site.

Usage

npx flowmap-scan login          # once — device-code sign-in, no password
npx flowmap-scan ./src          # scan + AI descriptions + publish
npx flowmap-scan whoami         # current user + AI credit balance

Options

| Flag | Meaning | | --- | --- | | --out <path> | Output path (default .flowmap/state.yaml) | | --no-ai | Raw structural scan — skip AI descriptions | | --no-push | Don't upload; leave the scan as a local file | | --full | Full re-scan: replaces the project on the server, wiping accumulated context (decisions / notes / known-issues) | | --project-id <id> | Project id (default: slugified package.json#name) | | --project-name <str> | Human project name |

A normal re-scan updates the code structure but keeps everything you and your AI have accumulated about the codebase. Only --full discards it.

Learn more at https://flow-map.link