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

@adlc/cli

v1.5.1

Published

Umbrella dispatcher for the @adlc suite - one install, one `adlc <tool>` command surface.

Readme

@adlc/cli

The umbrella dispatcher for the ADLC suite. It provides one stable command surface for Codex skills, hooks, CI, and humans:

adlc <tool> [args...]
adlc run <phase> [args...]
adlc accept [args...]

The dispatcher is a router. It adds no behavior to a tool run: argv is forwarded verbatim and the child exit code is propagated unchanged.

Why this exists

ADLC packages publish independently, but an agent harness needs a single stable prefix. A skill or hook that shells out to twenty different binaries is brittle, slower to document, and easier to route around. @adlc/cli installs the suite and makes every gate reachable through adlc <tool>.

Resolution model

The dispatcher resolves package-local binaries from its own @adlc/* dependencies. It does not search the user's PATH for tool names, so stale global binaries cannot silently satisfy a gate.

Usage

adlc --help
adlc --version
adlc spec-lint spec.md --json
adlc rails-guard --ticket T1 --record --json
adlc run p5 --ticket T1 --dir .adlc --json
adlc accept --ticket T1 --packet .adlc/packet.json --dir .adlc --json

Exit codes

Exit codes mirror the underlying tool:

  • 0: gate passes or command succeeds.
  • 1: operational error.
  • 2: gate fails.

Dispatcher-level failures, such as an unknown tool or missing package, exit 1.

ADLC phase

Cross-cutting. This is the delivery and invocation layer for the ADLC Codex integration.