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

@uptrack/cli

v1.0.0

Published

Manage Uptrack monitors, incidents and integrations from the command line.

Readme

@uptrack/cli

Manage Uptrack monitors, incidents and integrations from the terminal.

npm install -g @uptrack/cli

Requires Node 18+. No runtime dependencies.

Authenticate

Get a token from https://uptrack.site/settings, then:

uptrack auth                 # prompts, input is masked
uptrack auth status          # who am I, which instance
uptrack auth logout

The token is written to ~/.config/uptrack/config.json with mode 0600. UPTRACK_TOKEN and UPTRACK_URL override it, which is what you want in CI:

UPTRACK_TOKEN=$TOKEN uptrack monitors list --json

Self-hosted instance:

uptrack auth --url https://uptrack.internal.example.com

Monitors

uptrack monitors list
uptrack monitors get 7
uptrack monitors check
uptrack monitors create website --name "My Site" --url https://example.com --interval 300

Types: website, api, server, service, endpoint, port, heartbeat. Creating a heartbeat monitor prints the heartbeat URL to ping.

Incidents

uptrack incidents list
uptrack incidents get 3
uptrack incidents open --title "Payments degraded" --severity high
uptrack incidents resolve 3

Integrations

uptrack integrations list
uptrack integrations test namecheap
uptrack integrations sync cloudflare

Providers: namecheap, contabo, coolify, telegram, github, cloudflare, backup.

Scripting

Every command takes --json (-j) and exits non-zero on failure, so it pipes into jq:

uptrack monitors list --json | jq -r '.[] | select(.status != "operational") | .name'

License

MIT