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

maasy-cli

v0.2.2

Published

maasy — CLI/TUI para el Vibe agent de Maasy. Ver packages/cli/PLAN.md

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

maasymaasy

Keywords

Readme

@maasy/cli

CLI/TUI para el Vibe agent de Maasy. Habla con el mismo motor que el canvas web y WhatsApp: las cards que generás caen en la misma sesión vibe_session_*, así que abres el canvas en el browser y todo está ahí.

Plan de build, contrato y decisiones: PLAN.md.

Instalación (dev)

cd packages/cli
npm install
cp .env.example .env   # y completa MAASY_SUPABASE_ANON_KEY

MAASY_SUPABASE_ANON_KEY es la publishable key pública del front (VITE_SUPABASE_PUBLISHABLE_KEY). No se hardcodea en el repo.

Uso

npm run dev -- login                       # iniciar sesión (email/password)
npm run dev -- brands                       # listar tus marcas
npm run dev -- marca Pawers                 # fijar la marca activa
npm run dev -- vibe "crea 3 ideas premium"  # one-shot
npm run dev -- vibe "audit rápido" --nuevo  # forzar sesión fresca
npm run dev -- vibe "copy hero" --brand ON! # override de marca por turno
npm run dev                                 # TUI interactiva

El resultado incluye un link al canvas (/vibe-studio?session=…) para seguir en el browser.

Scripts

| Script | Qué hace | |---|---| | npm run dev -- <cmd> | corre desde TS con tsx | | npm run build | compila a dist/ | | npm run typecheck | tsc --noEmit | | npm test | vitest (parser SSE del transporte) |

Estado

Fase A (CLI funcional) lista. Fase B (TUI con canvas en vivo) y login por navegador (PKCE): ver checklist en PLAN.md.