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

@task-compass/cli

v0.1.1

Published

Agent-first CLI for Task Compass — tasks, habits, and notes from the terminal.

Readme

@task-compass/cli

Agent-first command line for Task Compass — operate your tasks, habits, and notes from a terminal or an AI agent. Requires a Task Compass sync account and Node ≥ 20.

npx @task-compass/cli --help

Login

Auth is an emailed one-time code, two-step so agents can drive it:

task-compass login --email [email protected]   # sends a 6-digit code
task-compass login --code 123456             # verifies it
task-compass whoami

On an interactive terminal, plain task-compass login prompts inline. The session is stored in ~/.config/task-compass/ and is fully independent of your web session — logout revokes only this device.

Commands

| Command | What it does | |---|---| | list | All live tasks. --status new\|open\|snoozed\|done, --tag <name\|id>, --query <text>, --limit <n> | | next | The focus queue head — what to work on now. --limit <n>, --tag <name\|id> | | get <id> | One task with its position-ordered subtasks | | create | --title <text> (required), --description <text>, --parent <id> for a subtask | | update <id> | --title, --description, --priority true\|false, --add-tag, --remove-tag, --subtask-mode list\|sequence | | complete <id> | Mark done; --comment <text> adds a comment. Habits record lastCompleted automatically | | reopen <id> | Back to open, clears snooze | | snooze <id> | --until <ISO datetime> or --hours <n>; --comment <text> | | comment <id> <text…> | Add a comment to the task history | | delete <id…> | Soft-delete. Batches over the mass-delete guard need --force; single deletes always pass | | tag list | List live tags (apply them via update --add-tag) | | login / logout / whoami | Session management |

JSON mode and exit codes

Every command takes --json and prints exactly one envelope to stdout:

{"ok": true, "data": …}
{"ok": false, "error": {"code": "not_found", "message": "No task with id …"}}

Exit codes map 1:1 to error.code, so scripts can branch without parsing:

| Exit | error.code | Meaning | |---|---|---| | 0 | — | success | | 1 | validation | bad input value, invalid state transition | | 2 | usage | unknown command/flag, missing required flag | | 3 | not_authenticated | no session — run task-compass login | | 4 | session_expired | refresh rejected — log in again | | 5 | network | request failed; at most one retry happened | | 6 | not_found | task/tag id or name didn't resolve | | 7 | guard_refused | mass-delete guard tripped without --force | | 8 | sync_denied | the account has no sync access |

list and next include computed effectiveStatus and dueForReopen fields: a done habit that is due again behaves as open without the CLI mutating anything — your view matches the web app's even when no tab is open.

Configuration

Production is built in. For a local/self-hosted Supabase backend:

| Env var | Default | |---|---| | TASK_COMPASS_SUPABASE_URL | production project URL | | TASK_COMPASS_SUPABASE_KEY | production publishable key | | TASK_COMPASS_CONFIG_DIR | ~/.config/task-compass |