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

taskara

v0.1.1

Published

The Taskara CLI and MCP server: an issue tracker an agent can drive.

Readme

taskara

The CLI and MCP server for Taskara — a team task manager that is also an issue tracker an agent can drive.

bun install -g taskara
taskara login

login signs you in, asks Taskara for a credential for your own agent — creating that agent and mirroring your team memberships if you have none — and stores it in ~/.taskara/credentials.json at mode 600. No admin has to be involved and no token is pasted anywhere. Your password is never stored: it buys one session, the session buys the credential, and the session is deleted before the command returns.

Then:

taskara task list --assignee me
taskara task claim CORE-12

Run taskara with no arguments for the full grammar.

Two surfaces, one core

  • The CLI is what a skill can reach. Agent skills are written in shell — they paste commands into Bash and branch on exit codes — so this covers the whole tracker contract rather than the read half of it.
  • The MCP server (taskara-mcp) is for conversation, where a tool call is natural and an exit code is not.

Both are the same operations. Neither is a subset of the other.

Exit codes

A script branches on these; stdout is always JSON and stderr is always the human line.

| | | |---|---| | 0 | ok | | 1 | usage — nothing was sent | | 2 | configuration — nothing was sent | | 3 | auth: absent, wrong, revoked, or not permitted | | 4 | not found | | 5 | conflict — somebody else holds it, or the row moved | | 6 | rejected | | 7 | server error — the outcome is unknown | | 8 | unreachable |

taskara task claim CORE-12 || handle_it works, and $(taskara task view CORE-12) always parses.

Configuration

login writes all of this. Set it by hand only in CI, where the environment wins over the stored file, field by field.

| | | |---|---| | TASKARA_API_URL | The API base URL. | | TASKARA_WORKSPACE_SLUG | One workspace holds the team; every read and write is scoped by it. | | TASKARA_AGENT_TOKEN | The agent credential, as a bearer token. | | TASKARA_AGENT_RUNTIME | CLAUDE_CODE, CODEX, OPENCLAW or HERMES. One binary serves all four; each runtime's config declares which it is. |

Requires Bun

Bundled as Bun modules and run with the Bun runtime — bun install -g taskara, not npm's.

Licence

MIT.