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

@ohos-ports/codesee

v0.728.0-beta.0

Published

CodeSee instrumentation and analysis to support developers with continuous code understanding

Readme

CodeSee CLI tools

Generating maps locally

  1. Navigate to the root of the repo you want to map

  2. Generate a map:

    npx codesee map --typescript -o my-repo.map.json
  3. If you don't already have an API token, generate one with yarn new:api-token

  4. Upload the map using your API token:

    npx codesee upload -a <your-token> -r <repo-url> -u http://localhost:5198 ./my-repo.map.json

Example

Let's say we want to generate a map of Maxime's little-do repository.

  1. Clone the repo:

    git clone https://github.com/deammer/little-do
  2. Navigate into the repo:

    cd little-do
  3. Generate a map and output it to the little-do.map.json file:

    npx codesee map --typescript -o little-do.map.json
  4. If you don't already have an API token, generate one with yarn new:api-token

  5. Upload the map to your local server:

    npx codesee upload -a 'your-api-token-in-single-quotes' -r 'https://github.com/deammer/little-do' -u http://localhost:5198 ./little-do.map.json
  6. Your map should now be visible on the /maps page!

Generating insights locally

  1. Navigate to the root of the repo of your choice

  2. Generate an insights file (see the available insight types in shared-constants):

    npx codesee insight -i commitCountLast30Days -o codesee.commitCountLast30Days.json
  3. If you don't already have an API token, generate one with yarn new:api-token

  4. Upload your insights to your local server:

    npx codesee upload -u http://localhost:5198 -t insight -a 'your-api-token-in-single-quotes' -r 'https://github.com/organization/repo-name' codesee.commitCountLast30Days.json