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

@mdb-ist/kube

v1.0.1

Published

CLI to manage Kanopy/Kubernetes setup and operations (kubeconfig, Helm, ksec secrets, Drone CI).

Readme

kube

A cross-platform CLI to manage Kanopy / Kubernetes setup and day-to-day operations: prerequisite installation, kubeconfig generation and login, ksec secrets, Drone CI secrets, deployment inspection, and diagnostics.

Works on Windows, macOS and Linux.

Install

npm install -g kube

Or run without installing:

npx kube

Usage

kube                 # launch the interactive menu
kube --help          # list every command and configuration flag
kube corp --help     # SSO session helper (harvest cookies for protected hosts)
kube keys            # GitHub key & auth manager (bash on macOS/Linux, PowerShell on Windows)

Running kube with no arguments opens an interactive menu covering setup, cluster access, secrets, deployment, Drone CI, and diagnostics.

Configuration

The tool ships no environment-specific defaults — values that point at a concrete cluster, registry, or domain must be supplied. Any command that needs a value it cannot find fails with a message naming the exact flag or variable to set, so nothing internal is baked into the package.

Every setting can be provided three ways, in precedence order:

  1. CLI flag — e.g. --namespace my-ns
  2. Environment variable — e.g. KUBE_NAMESPACE=my-ns
  3. .env file (optional, best-effort — never blocks the tool)

.env detection

When you run kube in any directory it will, in order:

  1. use --env-file <path> if given;
  2. otherwise load ./.env from the current working directory if present;
  3. otherwise load .env from the project root if present.

A missing .env never interrupts the tool.

Common flags

| Flag | Environment variable | Meaning | | --- | --- | --- | | --env-file <path> | — | Explicit environment file to load | | --namespace <ns> | KUBE_NAMESPACE | Kubernetes namespace | | --app-name <name> | KUBE_DEMO_NAME | App/release base name | | --staging-api <url> | KUBE_STAGING_API | Staging cluster API server | | --prod-api <url> | KUBE_PROD_API | Production cluster API server | | --domain <suffix> | KUBE_DOMAIN_SUFFIX | Ingress domain suffix | | --ecr-registry <host> | KUBE_ECR_REGISTRY | Container registry host | | --drone-url <url> | KUBE_DRONE_URL | Drone CI server URL | | --drone-repo <owner/repo> | KUBE_DRONE_REPO | Drone repository (falls back to the git remote) | | --helm-repo-url <url> | KUBE_HELM_REPO_URL | Helm chart repository URL | | --helm-repo-name <name> | KUBE_HELM_REPO_NAME | Helm repo alias (default charts) | | --helm-chart-version <v> | KUBE_HELM_CHART_VERSION | Helm chart version (default 4.25.0) | | --release-backend <name> | KUBE_RELEASE_BACKEND | Backend release name | | --release-frontend <name> | KUBE_RELEASE_FRONTEND | Frontend release name | | --release-merchant <name> | KUBE_RELEASE_MERCHANT | Merchant release name | | --ksec-secret-staging <n> | KUBE_KSEC_SECRET_STAGING | Staging ksec secret name | | --ksec-secret-prod <n> | KUBE_KSEC_SECRET_PROD | Production ksec secret name | | --cicd-token-secret <n> | KUBE_CICD_TOKEN_SECRET | CI/CD token secret (default kanopy-cicd-token) | | --ecr-secret-name <n> | KUBE_ECR_SECRET_NAME | ECR secret name (default ecr) | | --kanopy-config-dir <dir> | KUBE_KANOPY_CONFIG_DIR | Kanopy config dir under $HOME (default .kanopy) | | --kube-config-dir <dir> | KUBE_CONFIG_DIR | kubeconfig dir under $HOME (default .kube) |

Release, secret, and ingress-host names are derived from --app-name, --namespace, and --domain unless you override them explicitly.

Run kube --help for the complete, always-up-to-date list.

Example .env

KUBE_NAMESPACE=my-namespace
KUBE_DEMO_NAME=my-app
KUBE_STAGING_API=https://api.staging.example.com
KUBE_PROD_API=https://api.prod.example.com
KUBE_DOMAIN_SUFFIX=example.com
KUBE_ECR_REGISTRY=123456789012.dkr.ecr.us-east-1.amazonaws.com
KUBE_DRONE_URL=https://drone.example.com
KUBE_HELM_REPO_URL=https://charts.example.com

Requirements

Node.js >= 18. The tool installs / checks external CLIs it drives (kubectl, helm, kanopy-oidc, the ksec Helm plugin) and shells out to them. The corp helper additionally needs @playwright/test (npm i -D @playwright/test && npx playwright install chromium).

License

ISC — see LICENSE.