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

@tallwatch/cli

v0.3.2

Published

Tallwatch CLI — manage monitors and incidents from your terminal.

Readme

@tallwatch/cli

Tallwatch CLI. Thin client over the public REST API, plus UptimeRobot import.

Install

curl -fsSL https://tallwatch.com/install-cli.sh | bash

Or with npm (Node.js 20+):

npm install -g @tallwatch/cli@latest

From source in this monorepo:

pnpm --filter @tallwatch/cli build
pnpm tallwatch --help

Docs: docs.tallwatch.com/integrations/cli · Install page: tallwatch.com/cli

Browser login

tallwatch login

Prints a one-time code, opens the browser, and finishes when the app authorizes. Use --no-browser on remote SSH sessions.

Commands

Omit <id> on show / update / pause / resume / ack / resolve / postmortem / browse to pick interactively (searchable list in a TTY). Unique names also resolve. Scripts should pass a UUID or use --json.

tallwatch whoami
tallwatch status
tallwatch browse monitor
tallwatch logout
tallwatch update
tallwatch uninstall
tallwatch monitor list|show|create|update|pause|resume
tallwatch incident list|show|evidence|ack|resolve|reopen|postmortem
tallwatch oncall now
tallwatch status-page list
tallwatch test --url https://…
tallwatch import uptimerobot --file ./monitors.json [--apply] [--yes]

Run tallwatch help or tallwatch <command> --help for flag reference.

Auth

  • tallwatch login / tallwatch logout — browser device login, or clear ~/.config/tallwatch/config.json
  • Env: TALLWATCH_API_KEY (tw_live_…), optional TALLWATCH_API_URL
  • The CLI never prints the full key after validation

Update / uninstall

tallwatch update      # install latest from npm (uses the npm next to this Node)
tallwatch uninstall   # clear login + remove the global package

If npm uninstall -g @tallwatch/cli does nothing, you are on a different Node than the one that owns tallwatch (common with fnm/nvm vs Homebrew). Prefer tallwatch uninstall, or run uninstall with the same Node that which tallwatch uses.

UptimeRobot import

Export monitors:

curl -X POST https://api.uptimerobot.com/v2/getMonitors \
  -H "Content-Type: application/json" \
  -d '{"api_key":"YOUR_UR_KEY","format":"json","custom_http_statuses":1,"custom_http_headers":1}' \
  > monitors.json

Prefer readable fields: type: "http" | "keyword", keyword_type: "contains" | "not_contains", http_method: "GET". Numeric UptimeRobot codes still map. Ping / port / heartbeat are skipped. Creates use three default regions (fra1, iad1, sgp1). Dry-run is the default; --apply writes. App UI: Monitors → Import. Sample: docs/fixtures/uptimerobot-sample.json.

Publish (maintainers)

@tallwatch/cli depends on @tallwatch/contracts on npm. Publish both in order:

npm login
pnpm publish:cli

Requires the @tallwatch npm org and a clean git tree is not enforced (--no-git-checks).

Notes

  • tallwatch test runs from the API host (SSRF-filtered), not from probe regions.
  • Reuses @tallwatch/contracts Zod schemas for create bodies — no second API dialect.
  • Destructive pause/import requires confirmation unless --yes.