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

trace-mapper

v1.0.4

Published

Trace CLI to map API flows visually across your codebase

Readme

trace-mapper

trace-mapper is a CLI tool designed to scan your codebase, map your API flows, and generate visual representations or structured JSON data.

Installation

You can run trace-mapper directly using npx (no installation required):

npx trace-mapper map

Or you can install it globally:

npm install -g trace-mapper

If installed globally, you can run:

trace-mapper map

Usage

Navigate to your project directory and run the map (or scan) command:

npx trace-mapper map [options]

Options

| Option | Description | Default | | ------ | ----------- | ------- | | -d, --dir <directory> | Directory to scan | Current working directory | | -k, --key <key> | API key for trace.dev. Saves to ~/.trace/config.json. | (reads from $TRACE_API_KEY) | | -n, --name <name> | Name for the mapped flow | | | --json | Output raw JSON data instead of formatted logs (useful for piping) | false | | --depth <number> | Max directory depth to traverse during the scan | 10 | | --include <globs> | Extra glob patterns to include (comma-separated) | | | --exclude <globs> | Extra ignore patterns to exclude (comma-separated) | | | --no-color | Disable color output in the terminal | |

Examples

Scan the current directory

npx trace-mapper map

Scan a specific directory with a custom name

npx trace-mapper map -d ./my-backend-service -n "Backend API Flow"

Output results as JSON and save to a file

npx trace-mapper map --json > api-flow.json

Set API key for trace.dev

npx trace-mapper map -k your_api_key_here

(Your key is saved to ~/.trace/config.json for future use).

Configuration

If you don't want to pass your API key via the CLI flag every time, you can also set it using the TRACE_API_KEY environment variable in your project's .env file or terminal environment.

🤝 Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

  1. Fork the repository
  2. Create your feature branch (git checkout -b feature/amazing-feature)
  3. Commit your changes (git commit -m 'feat: add amazing feature')
  4. Push to the branch (git push origin feature/amazing-feature)
  5. Open a Pull Request

📝 License

This project is licensed under the ISC License.

👨‍💻 Author

Parth Mongia

📮 Support