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

@jc_stack/ez-github

v0.1.0-beta.7

Published

Native Git and GitHub CLI with private per-agent profiles for Ez

Readme

ez-github

Thin native GitHub CLI and Git plugin for Ez. Private per-agent profile and writable repository volume; no provider API implementation or workflow engine.

Requires Node 22+, Docker/Compose and Ez with the cancellation fix (manager release 0.1.0-beta.60 or newer). Obtain @jc_stack/[email protected] with npm pack @jc_stack/[email protected] --ignore-scripts, extract into a permanent private tools directory, and inspect the extracted package.

Inspect this directory with ez plugins inspect github --source /absolute/package, then install with the inspected source and revision and run ez plugins start github. Read skills/github/SKILL.md for complete agent-owned OAuth setup and verification.

ez github gh --help and ez github git --help expose upstream tools unchanged. ez github doctor verifies authentication with a nonzero exit when unavailable. Native GitHub JSON is available with gh api and supported gh --json options.

Credentials persist in /state; repositories persist in /repos. The PA workspace is read-only. A local clone transfers committed history, not uncommitted/untracked files. HTTPS Git uses gh auth setup-git. No manual token or GitHub App registration needed. OAuth permissions are broad within the connected user's existing GitHub authority; use a dedicated account when separation is wanted. Container tokens are private files, not encrypted by a keyring. No unattended identity creation or token display.

Uninstall preserves data. Revocation is separate in GitHub's authorized applications. Rollback retains volumes; do not run concurrent writers on one repository. Test with pnpm run verify, pnpm run release:check, Docker build and manager dispatch. Live GitHub verification needs consent.

Testing beta: Debian supplies Git and the signed upstream GitHub CLI repository supplies gh at image build; the installed image is retained by Ez's source revision. Capture gh --version and git --version during QA. Fresh isolated Docker installation and PA authentication are tested; a separate machine/reboot and a fresh OAuth consent in that environment remain stable-release QA.

Requires Ez core 0.1.0-beta.60 or newer for the manifest example. Older cores refuse the update and retain the installed version.

Kanban

ez kanban gives agents basic task-board operations: board, list, show, add, move, set and comment, with JSON output and a readback after every write. The verbs are tracker-neutral; this adapter stores the board in a GitHub Project through the private profile, so another tracker can later provide the same commands. It holds no workflow rules. Example: ez kanban list --board OWNER/NUMBER --column Ready. The login needs the project scope. See skills/kanban/SKILL.md.

Read-only work queue preflight

ez github-work --project PROJECT_NODE_ID --field Role=CIO --field Status=Ready --require-metadata reads the complete Project through the private GitHub profile, returning only eligibility, IDs and a stable fingerprint. Field names/values are caller supplied; this adapter contains no role, model or workflow routing. ez-work JSON on an issue records schemaVersion:1, identity, optional notBefore and freshUntil; requiring metadata also requires a valid unexpired freshness clock. Missing provider/schema coverage is an error, never empty work. A malformed, ambiguous or over-long (200+ characters) ez-work block on any open item blocks the whole queue (the check errors, fail closed) by design; fix or remove the block to unblock it. Filter fields must be single-select or text, and an unreadable value for a filtered field is an error. This command makes no task writes and starts no agent. Core's installed plugin preflight calls it before creating an LLM run. Existing native github/Git commands are unchanged. Managed snippet: unnecessary; installed help/skill owns discovery.

For coordination, github-work --project PROJECT_NODE_ID --observe-all fingerprints complete Project state, including waiting, closed and archived items. It ignores queue clocks/metadata and permits a changed-state check even for an empty Project. Use it with native changed-mode admission; keep role queue selection on the filtered path.