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

@prajwolkc/stk

v0.9.0

Published

One CLI to deploy, monitor, debug, and learn about your entire stack. Infrastructure monitoring, knowledge base brain, deploy watching, and GitHub issues — all from one command.

Readme

stk

One CLI to deploy, monitor, and debug your entire stack.

Stop opening 5 dashboards. stk checks your services, watches your deploys, syncs your env vars, tails your logs, and manages your issues — all from one command.

Install

npm install -g @prajwolkc/stk

Quick Start

cd my-project
stk init                      # auto-detect your services
stk init --template saas      # or use a starter template
stk doctor                    # diagnose any misconfig
stk health                    # check everything
stk status                    # one-line summary of your whole stack

Commands

| Command | Description | |---------|-------------| | stk init | Initialize config (auto-detect or --template saas\|api\|fullstack\|static\|fly\|aws) | | stk status | One-line summary: git, services, deploys, issues | | stk health | Health check all configured services | | stk doctor | Diagnose misconfig, missing env vars, and suggest fixes | | stk deploy | Git push + watch deploy providers | | stk env pull | Pull env vars from Vercel + Railway into .env.pulled | | stk env diff | Show what's in your local .env | | stk logs | Tail logs from Railway, Vercel, Fly, or Render | | stk logs -p vercel | Logs from a specific provider | | stk todo ls | List open GitHub issues | | stk todo add "title" | Create a GitHub issue | | stk todo close 42 | Close an issue |

Supported Services

Deploy providers: Railway, Vercel, Fly.io, Render, AWS Databases: PostgreSQL, MongoDB, Redis, Supabase Storage & billing: Cloudflare R2, Stripe Custom: Add your own via plugins

Configuration

stk init creates a stk.config.json in your project root:

{
  "name": "my-saas",
  "services": {
    "vercel": true,
    "railway": true,
    "database": true,
    "redis": true,
    "stripe": true,
    "r2": true
  },
  "deploy": {
    "branch": "main",
    "providers": ["vercel", "railway"]
  }
}

Only configured services are checked — no noise from services you don't use.

If no config file exists, stk auto-detects services from your environment variables.

Templates

stk init --list-templates

| Template | Stack | |----------|-------| | saas | Vercel + Railway + PostgreSQL + Redis + Stripe + R2 | | api | Railway + PostgreSQL + Redis | | fullstack | Vercel + Railway + Supabase + Stripe | | static | Vercel only | | fly | Fly.io + PostgreSQL + Redis | | aws | AWS + PostgreSQL + Redis |

Doctor

stk doctor scans your config and environment to catch issues before they bite:

$ stk doctor

  my-saas — Doctor
  ─────────────────────────────────────────
  ✓  railway      Configured correctly
  ✗  vercel       Missing required: VERCEL_TOKEN
                   See https://vercel.com/account/tokens
  !  database     Missing optional: RAILWAY_PROJECT_ID
                   Some features need these for full functionality
  ✓  stripe       Configured correctly

Plugins

Add custom services without forking. Create .stk/plugins/my-service.mjs:

export default {
  name: "my-plugin",
  services: {
    myservice: {
      name: "My Service",
      envVars: ["MY_SERVICE_TOKEN"],
      healthCheck: async () => {
        const token = process.env.MY_SERVICE_TOKEN;
        if (!token) {
          return { name: "My Service", status: "skipped", detail: "MY_SERVICE_TOKEN not set" };
        }
        // Your check logic here
        return { name: "My Service", status: "healthy", detail: "connected" };
      }
    }
  }
};

Plugins are automatically loaded by stk health and stk health --all.

Environment Variables

# Deploy providers
RAILWAY_API_TOKEN=
VERCEL_TOKEN=
FLY_API_TOKEN=
FLY_APP_NAME=              # needed for stk logs -p fly
RENDER_API_KEY=
AWS_ACCESS_KEY_ID= / AWS_SECRET_ACCESS_KEY=

# Databases
DATABASE_URL=
MONGODB_URL=
REDIS_URL=
SUPABASE_URL= / SUPABASE_SERVICE_KEY=

# Storage & billing
CLOUDFLARE_ACCOUNT_ID= / CLOUDFLARE_API_TOKEN=
STRIPE_SECRET_KEY=

# GitHub (for stk todo)
GITHUB_TOKEN=
GITHUB_REPO=owner/repo   # or auto-detected from git remote

Claude Code / MCP Integration

stk ships with a built-in MCP server so Claude Code can use your infrastructure as native tools.

Setup

  1. Install stk globally:
npm install -g @prajwolkc/stk
  1. Add to your project's .mcp.json (create it in your project root):
{
  "mcpServers": {
    "stk": {
      "command": "stk-mcp",
      "args": []
    }
  }
}
  1. Restart Claude Code. Approve the stk MCP server when prompted.

What Claude can do

| Tool | Description | |------|-------------| | stk_health | Check if all services are up before writing code | | stk_status | Full overview: git, services, deploys, issues | | stk_doctor | Diagnose misconfig and missing env vars | | stk_logs | Read production logs to understand bugs | | stk_todo_list | See what needs to be worked on | | stk_todo_add | Create GitHub issues | | stk_deploy | Push code and trigger deploys | | stk_config | Read the project's stack config |

Example prompts

  • "Check if all my services are healthy"
  • "What errors are in my production logs?"
  • "What should I work on next?"
  • "Deploy this and verify it worked"

Development

git clone https://github.com/Harden43/stk.git
cd stk
npm install
npm run dev -- health --all     # run in dev mode
npm test                        # run tests
npm run build                   # compile TypeScript

License

MIT