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

@deftai/canonical

v0.3.0

Published

The canonical pack: a compact, deterministic agent-workflow framework -- xBRIEF-based state, 20 CLI verbs, fail-closed git gates. Install globally, run `canon init` in any project.

Readme

canonical

A compact, deterministic agent-workflow framework: 7 rule files an AI agent reads, 20 CLI verbs that make the workflow checkable, and fail-closed git gates. The pack lives in content/ (root: content/canonical.md; verb contracts: content/canonical-tasks.md).

Install

npm i -g @deftai/canonical

Requirements: Node ≥ 20, git. For the task <verb> surface, install go-task ≥ 3.33 separately (brew install go-task / scoop install task / see taskfile.dev) — it is not an npm dependency. Every verb also works directly as canon <verb> without go-task.

Use in a project

cd my-project        # a git repo (run `git init` first if new)
canon init

This deposits .canonical/core/ (the rule pack + Taskfile + hooks), writes an AGENTS.md managed section pointing your AI agent at the rules, wires the root Taskfile.yml include (verbs are bare: task check, task scope:new -- "title"), scaffolds xbrief/ (the durable work state), and installs git hooks.

Then open the project with your AI agent and say:

I want to make an app that does X, help me set this up.

The pack's kickoff flow interviews you, generates the project brief + one scope per feature with acceptance criteria, and renders the roadmap. canon update refreshes the deposit after upgrades; canon init is idempotent.

Exit codes everywhere: 0 ok · 1 rejected/not ready · 2 misconfig/error. When invoking through go-task, use task -x <verb> to propagate the verb's exact exit code (plain task wraps failures as 201).

Layout

  • content/ — the canonical pack (deposited into consumer projects)
  • src/ — the canon CLI: src/types (contracts), domain modules, src/cli (verbs)
  • tasks/ — go-task fragments + engine dispatch shims
  • .githooks/ — pre-commit / pre-push gates
  • docs/ — maintainer docs (repo-only, not in the npm package): ARCHITECTURE.md · DEPLOY.md · manual-test-plan.md (end-to-end walkthrough on a throwaway Wordle app)

Develop

pnpm install
pnpm run build     # tsc
pnpm run lint      # biome
pnpm run test      # vitest + coverage report

Local install for testing: npm pack then npm i -g ./deftai-canonical-*.tgz.

Release

Update CHANGELOG.md, merge, then tag: git tag v<X.Y.Z> && git push origin v<X.Y.Z> — the publish workflow builds and publishes to npm with provenance.

License

MIT