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

@simplafy-tec/adk

v0.1.0

Published

CLI do ADK da Simplafy — cria, valida e publica agentes, tools e jornadas no Hub.

Readme

@simplafy-tec/adk

CLI do ADK da Simplafy. Node ≥ 20, sem postinstall.

npx @simplafy-tec/adk <comando>

Comandos

| Comando | O que faz | | -------------------------------------- | ----------------------------------------------------------------------------------------------------- | | doctor | Confere node/python 3.12/uv/git contra GET /api/v1/adk/policy (fallback embutido) | | login · whoami · orgs · logout | OAuth do Hub: DCR, PKCE S256, callback em 127.0.0.1 | | init tool\|mcp\|app <nome> | Esqueleto do componente (manifest.yaml, tools/<nome>.py, pyproject.toml uv, testes) | | build | Contrato + scanLeaks + uv lock + ruff check + tamanho ≤ política. Saída JSON {issues, checks} | | test · dev | uv run pytest · watch que revalida e executa o handler com dev/sample-input.json | | validate | Valida os artefatos localmente, sem falar com o Hub | | plan · deploy (apply) | POST /api/v1/adk/{tools\|agents\|journeys}/{plan\|apply}?orgId= | | mcp-server | stdio: list_components, get_contract, get_policy, validate, plan |

Ambiente

  • ADK_HUB_URL — base da API do Hub (ex.: https://api-hub-v2-staging.simplafy.com.br).
  • ADK_TOKEN — modo headless (API key sk_… ou JWT). Ganha do login: o CI precisa ser previsível, e a credencial da máquina de quem rodou por último não pode vazar para dentro dele. Com ADK_TOKEN, --org é obrigatório.
  • ADK_CONFIG_DIR — sobrescreve ~/.config/simplafy-adk (testes).

adk login grava ~/.config/simplafy-adk/credentials.json com permissão 0600, indexado por URL do Hub, e renova o access token sozinho (60 s antes do fim). adk logout revoga antes de apagar — apagar só o arquivo deixaria um refresh token vivo por 30 dias do lado do servidor.

Ordem e tolerância a falha no deploy

Os artefatos sobem na ordem tool → agent → journey: um agente pode referenciar a tool que este mesmo apply cria, e a jornada pode acionar os dois. Um artefato que falha não aborta os demais — o relatório sai completo e o exit code é 1. --json emite {artefatos: [{arquivo, kind, slug, action, blocking, pending, applied}]}.

Só entram as pastas cujo orgs/<pasta>/org.yaml declara o --org no --env pedido (default staging). Pasta sem org.yaml fica de fora: o silêncio nega.

init e segredo

O template nasce com .gitignore cobrindo .env* e .venv/, e sem CLAUDE.md. O build varre todo o pacote menos .env* — é o lugar certo do segredo local, e escaneá-lo reprovaria o uso correto. Credencial de produção é referenciada por nome e resolvida no Hub.

kind: mcp e kind: app geram esqueleto, mas o deploy é recusado pelo servidor com unknown_kind até a fatia N10.