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

@vforsh/kuma

v0.1.0

Published

Bun CLI for Uptime Kuma monitoring

Readme

@vforsh/kuma

Bun CLI for Uptime Kuma monitoring.

Install (dev)

bun install
./bin/kuma --help

Auth

Preferred — env vars:

export KUMA_URL="https://uptime.example.com"
export KUMA_USERNAME="admin"
export KUMA_PASSWORD="secret"

Or store locally:

kuma config set url https://uptime.example.com
kuma config set username admin
echo "$KUMA_PASSWORD" | kuma config set password

Precedence: env > config file.

Examples

kuma info
kuma monitors list
kuma monitors get 1
kuma monitors add http "My Site" https://example.com --interval 60
kuma monitors pause 1
kuma monitors resume 1
kuma monitors delete 1
kuma notifications list
kuma status-pages list
kuma maintenance list
kuma tags list

Output modes

  • default: human-friendly tables
  • --plain: stable line output (ids only)
  • --json: stable JSON output

Global flags

--json          machine-readable JSON output
--plain         stable line-based output (ids/names only)
-q, --quiet     suppress logs
-v, --verbose   verbose diagnostics to stderr
--no-color      disable colored output
--url <url>     Kuma server URL (overrides config)
--timeout <ms>  socket timeout in ms (default: 30000)

Config

Stored at ~/.config/kuma/config.json (XDG-compliant).

kuma config path           # print config file path
kuma config get            # show config (password redacted)
kuma config set <key> [value]  # set a key
kuma config unset <key>    # remove a key

Valid keys: url, username, password.

Password is never accepted via argv — always use stdin or --from-env.