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

canonweave

v0.3.0

Published

GitHub-native artifact traceability: files as the system of record, deterministic derivation graph, suspect links, AI reconcile behind a human PR gate. Zero runtime dependencies.

Readme

Canonweave

GitHub-native artifact traceability. Every product artifact — brief, requirements, acceptance criteria, architecture, test plan — is a Markdown file that declares what it derives from. Canonweave builds the derivation graph, fingerprints every link, flags stale dependents the moment an upstream changes, and gates CI until a human reconciles the thread.

  • Files are the system of record — versioned, diffable, greppable; no hosted service, no database, no telemetry. State is your git history.
  • Deterministic — same inputs, byte-identical graph.json; CRLF-safe on Windows checkouts; proven by a determinism snapshot in CI.
  • Zero runtime dependencies — Node builtins only, enforced in CI. The dependency tree IS the audit.
  • Human gate on all AI output — the reconcile drafter only ever produces a proposal for review; nothing is auto-applied.

Try it

node packages/cli/bin/canonweave.mjs init --template generic-software --dir /tmp/demo
cd /tmp/demo && node <this-repo>/packages/cli/bin/canonweave.mjs check

Full walkthrough: docs/quickstart.md

Layout

| path | what | |---|---| | packages/engine | zero-dep core: config, schema, ontology, resolvers, fingerprints, graph, gates, reconcile | | packages/cli | the canonweave binary: init/build/check/gate/fingerprint/clear/reconcile/sync-issues/serve/selftest | | packages/reconcile-action | the reconcile GitHub Action: idempotent AI fix PRs for suspect links (docs/reconcile.md) | | packages/action | the gate as a GitHub Action: inline annotations, sticky PR comment, job summary, fork-safe (usage) | | templates/ | generic-software, product-lifecycle ontology templates | | examples/demo-repo | living fixture: docs demo + CI drift check | | docs/ | quickstart · file formats · gate profiles · reconcile loop · issues/board projection · dashboard · security |

Verify a checkout

npm test   # = CLI selftest + action selftest + determinism snapshot + zero-deps, no install step

Status: WS1 (core extraction) and WS2 (Action + demo + quickstart) complete — engine, CLI, templates, gate action with hermetic GitHub-environment selftest, consumer workflow template, branch-protection recipe, CI matrix (ubuntu/windows/macos × Node 20/22/24). WS5 (release engineering) complete: Apache-2.0, SHA-pinned CI, CodeQL + Scorecard (activate at the public flip), tag-triggered provenance release pipeline (docs/releasing.md). The repo stays private until the dogfood gate (AIW-231) passes — the launch flip is a one-sitting checklist in the runbook.