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

@ccgrapher/cli

v0.4.0

Published

Command line interface for ccgrapher: lint, render, codegen and ingest.

Readme

@ccgrapher/cli

Command line interface for ccgrapher — a linter for agent workflows.

npx @ccgrapher/cli lint my-workflow.yaml
ccg lint    <spec.yaml>...            find fake edges and wasted sequencing
ccg render  <spec.yaml> -o out.svg    draw it (svg | mermaid | excalidraw)
ccg codegen <spec.yaml> -t <target>   emit orchestration code
ccg ingest  <orchestration.ts>        reconstruct a spec from existing code
ccg plan    <spec.yaml>               what can run at once, wave by wave
ccg retro   <owner/repo>              rebuild the as-merged workflow from PR history
ccg run     <spec.yaml> --impl <mod>  execute the spec and write a trace
ccg serve   <trace-dir>               stream a run's trace over SSE
ccg trace stats <run.jsonl|dir>       durations and cost, summarised
ccg trace audit <run.jsonl|dir> --spec <spec.yaml>
                                      hold a run against what its spec declared

An edge only exists if real data passes along it. Most workflows are typed as a straight chain out of habit, so most edges are fake; delete them and the graph goes wide instead of tall.

  error  FAKE_EDGE      review_a -> review_b carries nothing
  error  MISSING_INPUT  review_b requires 'repo' but no inbound edge carries it

  Critical path: 6 layers -> 4 layers (2 fewer after repair)

Exit code is 0 when clean, 1 when there are errors, 2 on bad usage.


Part of ccgrapher. Apache-2.0 — see LICENSE and NOTICE.