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

komplian

v0.8.12

Published

Komplian CLI: setup (all-in-one), onboard, Postman, localhost, mcp-tools, skills (Cursor rules), db (psql). Node 18+.

Readme

komplian (npm CLI)

Quickstart (práctico)

  1. Instala GitHub CLI, git, Node 18+.
  2. Login: gh auth login -h github.com -s repo -s read:org -w
  3. Elige flujo:
    • Full (onboarding completo): npx komplian setup
    • Lean (rápido para empezar a programar con IA): npx komplian setup --lean

Qué hace cada modo

  • Full (setup): onboard → postman → mcp-tools → skills → db:all:dev → localhost
  • Lean (setup --lean): onboard → skills → localhost --minimal

Arquitectura base considerada por el CLI/rules

  • app, web, docs en Vercel
  • api en Google Cloud Run
  • admin en GCP VM + Caddy + Tailscale (no Vercel)
  • Entornos canónicos: production y staging

npm ERR! ETARGET / “No matching version” (también si falló postman, no solo onboard): es el mismo paquete npm. Usa npx komplian postman --yes sin @0.4.x; comprueba npm config get registryhttps://registry.npmjs.org/; npm cache clean --force. Detalle: ONBOARDING.md en el monorepo.

Postman (colección + entornos)

  1. En Postman usa una cuenta con email @komplian.com (o añade ese email a tu perfil).
  2. Crea una API key: Settings → API keys → Generate.
  3. Sincronizar (la primera vez en terminal interactiva te pide la API key y la guarda en ~/.komplian/postman-api-key; no hace falta export después):
npx komplian postman --yes

Opcional: npx komplian postman login solo para guardar o rotar la clave sin ejecutar el sync.

Opcional: export POSTMAN_API_KEY=… solo para la sesión actual (tiene prioridad sobre el archivo).

El comando llama a GET https://api.getpostman.com/me y solo continúa si el email de la cuenta es @komplian.com. Si ya existen la colección Komplian API y los entornos con el mismo nombre en ese workspace, se actualizan; si no, se crean.

Variables de la API Komplian (apiKey, adminApiKey, workspaceId, …) se rellenan en Postman automáticamente si están en process.env o en archivos .env (busca api/.env, .env, etc.; o KOMPLIAN_DOTENV / --dotenv ruta). Nombres típicos: API_KEY, ADMIN_API_KEY, KOMPLIAN_WORKSPACE_ID. Los JSON exportados en ~/.komplian/postman-export/ (o --out) no incluyen secretos (para no commitearlos).

  • Solo exportar archivos (sin subir por API): npx komplian postman --yes --export-only
  • Otro workspace: POSTMAN_WORKSPACE_ID=<id>
  • Ruta alternativa del archivo de clave Postman: KOMPLIAN_POSTMAN_KEY_FILE

Seguridad (CLI Postman): clave en ~/.komplian/ (permisos reforzados por el CLI), prompt sin eco, errores redactados; detalle técnico arriba. Normativa del equipo: archivo SECURITY.md en la raíz del monorepo Komplian (no va en el paquete npm).

No OAuth App registration — gh uses GitHub’s built-in flow. Default workspace: current working directory (process.cwd()), not ~/komplian. Pass a path as last argument to clone elsewhere.
Dependencies: repos with package-lock.json use npm ci (does not modify the lockfile, so no spurious git changes). Repos without a lockfile use npm install --no-package-lock so onboarding does not create a new package-lock.json. Yarn / pnpm repos use frozen lock installs when yarn / pnpm is on PATH. Unless KOMPLIAN_NPM_AUDIT=1, npm runs with --no-audit --no-fund.

Maintainers: publish from this package directory (where this package.json lives), not from unrelated monorepo roots:

cd path/to/komplian-cli-package
npm login
npm publish --access public

Bump version before each publish.

If publish fails with 403 / 2FA: enable 2FA on npm (Account → Security) or use a granular token with publish rights; set NPM_TOKEN in CI (see .github/workflows/publish-komplian-npm.yml).