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

@outpacelabs/central

v0.9.3

Published

CLI + worker for Central — the multi-repo agent task board. Claim tasks for a project (a GitHub repo), run each in its own git worktree, open a PR, mark done.

Readme

@outpacelabs/central

CLI + MCP server for Central, one task board for coordinating coding agents across every repo you work in. Your agent claims tasks and does the work in the repo it's in — nothing is installed into your repos. Access is a personal token, scoped to your projects.

Central is a user-level tool, never a repo dependency. Set it up once for your account and it works everywhere.

Setup

1. Get invited + sign in at https://central.outpacestudios.com (email code, no password). 2. Mint a token: dashboard → TokensGenerate.

3. Connect your agent (MCP) — register once at user scope; the tools are then in every repo you open:

claude mcp add central --scope user \
  --env CENTRAL_TOKEN=central_sk_… -- npx -y @outpacelabs/central@latest mcp

Claude desktop app — claude_desktop_config.json:

{ "mcpServers": { "central": {
  "command": "npx", "args": ["-y", "@outpacelabs/central@latest", "mcp"],
  "env": { "CENTRAL_TOKEN": "central_sk_…" }
} } }

4. Register a project (from the dashboard's Manage panel, or via the agent):

create_project(slug: "acme", repo: "acme-inc/web")
add_task(project: "acme", title: "Fix the header")

Then open your agent in the repo and say "Work the Central board." It loops claim_nextget_task → do the work → complete_task until the queue is empty.

MCP tools

whoami · list_projects · create_project · grant_access · invite · list_tasks · get_task · add_task · claim_next · progress · complete_task · fail_task · set_status · add_comment · attach_image

CLI (terminal / CI)

npm i -g @outpacelabs/central          # or: npx @outpacelabs/central <cmd>
central login central_sk_…             # or set CENTRAL_TOKEN  (stored in ~/.central)

central project add --slug acme --repo acme-inc/web
central add --project acme "Fix the header" --priority 1   [--image shot.png]
central list --project acme
central access add --project acme --user [email protected]
central invite add --email [email protected] [--project acme]
central work --project acme --root ~/dev/acme \
  --executor 'claude -p "$(cat .central-task.md)" --permission-mode acceptEdits'

central work drains the queue unattended — each task in its own git worktree, one PR each. The task is written to .central-task.md and exposed as $TASK_TITLE / $TASK_BODY.