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

@benup/bensdk

v1.13.12

Published

<div align="center"> <img src="https://img.shields.io/badge/Status-Stable-green" alt="Status: Stable"> <img src="https://img.shields.io/badge/Version-1.12.2-blue" alt="Version: 1.12.2"> </div>

Readme

BenSDK CLI

O BenSDK CLI gera o scaffolding de projetos de integração de benefícios para o ecossistema Benup. Com um único comando você tem um projeto TypeScript pronto com máquina de estados, handlers, testes unitários e servidor local para testar contra a API real do parceiro.

Instalação

npm i -g @benup/bensdk-cli

Uso

ben init <BENEFIT-ID>

O CLI vai perguntar:

  • Quais actions o benefício suporta (RECHARGE, DEDUCTION, GRANT_DEPENDENT, REVOKE_DEPENDENT)
  • Categoria do benefício (opcional)
  • Descrição curta (opcional)
  • Configurar git + husky com pre-commit (recomendado)

Ao final, o projeto estará instalado e pronto para uso.

O que é gerado

<BENEFIT-ID>/
├── src/
│   ├── benefit-definition.ts    # Maquina de estados + schemas (ponto de entrada)
│   ├── handlers/                # Gerados via npm run generate
│   └── lib/                     # Utilitarios e mocks
├── bin/
│   ├── cli/                     # npm run generate
│   ├── server/                  # npm run dev:start
│   └── docs/                    # npm run docs:update
├── context.config.ts            # Mock context para testes unitarios
├── ICON.png                     # Icone do beneficio
└── dev-test.example.json        # Modelo de credenciais para testes locais

Scripts do projeto gerado

| Comando | Descricao | |---------|-----------| | npm run generate | Gera handlers e testes baseados no benefit-definition.ts | | npm run dev:start | Sobe servidor local para testar handlers contra a API real do parceiro | | npm run docs:update | Regenera os diagramas Mermaid do README a partir do benefit-definition.ts atual | | npm run test | Executa os testes unitarios com Vitest | | npm run start | Abre o painel visual da maquina de estados | | npm run lint | Valida tipos TypeScript, formatacao e linting |

Testando localmente com dev:start

Copie dev-test.example.json para dev-test.json, preencha com as credenciais reais e suba o servidor:

npm run dev:start

Com isso voce consegue executar qualquer handler chamando POST http://localhost:3000 com o payload da action, autenticando via o auth.handler definido no benefit-definition.ts e batendo na API real do parceiro. Veja docs/DEV_SERVER.md no projeto gerado para documentacao completa.

Publicacao

Utilize o maria-cli para publicar o beneficio:

maria benefit deploy -r <link-ssh-do-repositorio> -n <BENEFIT-ID>