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

@rensoai/code-graph

v1.4.2

Published

Dependency graph analyzer for code, tests, docs, and policy surfaces. Bundles the prebuilt code_graph + code_graph-mcp binaries via per-platform sub-packages.

Readme

npm distribution wrapper

This package is still published for distribution compatibility, but customer-facing install docs live at https://cg.renso.ai/docs#install and document only the curl/script installer.

Uses the esbuild/swc/turbo platform-package pattern: a meta package @rensoai/code-graph declares per-platform sub-packages as optionalDependencies. npm picks the right one at install time. No postinstall network call.

Files in this directory

  • package.json — meta package manifest (@rensoai/code-graph)
  • bin/code_graph.js, bin/code_graph-mcp.js — tiny Node shims that resolve the matching platform sub-package and spawn its binary
  • platforms/ — per-platform sub-package templates, generated at release time

Sub-packages published

| Sub-package name | Binary target | |-----------------------------------|--------------------------| | @rensoai/code-graph-linux-x64-gnu | x86_64-unknown-linux-gnu | | @rensoai/code-graph-linux-arm64-gnu | aarch64-unknown-linux-gnu | | @rensoai/code-graph-darwin-x64 | x86_64-apple-darwin | | @rensoai/code-graph-darwin-arm64 | aarch64-apple-darwin | | @rensoai/code-graph-win32-x64 | x86_64-pc-windows-msvc |

Publish order

The publish-npm job in .github/workflows/release.yml:

  1. Templates each platform package.json with the current version.
  2. Copies the matching binary into each platform sub-package directory.
  3. Publishes all five platform sub-packages (npm publish each).
  4. Waits 60 seconds for registry CDN propagation.
  5. Publishes the meta package.

Order matters. Publishing the meta package before platform sub-packages propagate causes warm-cache install failures.