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-contract

v0.1.0

Published

Contrato de especificação do ADK da Simplafy — validadores puros, códigos de erro estáveis e política.

Vulnerabilities

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

Links

Git

Maintainers

luiserlacherluiserlacher

Keywords

Readme

@simplafy-tec/adk-contract

Funções puras (sem Prisma, Nest, filesystem ou rede) que definem o contrato de especificação do ADK. É o mesmo motor dos dois lados da fronteira: o que o adk build reprova é o que o POST /api/v1/adk/*/apply reprova, com o mesmo code e o mesmo path.

Exporta

  • SPEC_VERSION ('v1'), SUPPORTED_SPEC_VERSIONS (janela N / N-1), SPEC_KINDS.
  • SpecIssue { code: SpecIssueCode, path, message } — SpecIssueCode é união fechada: código inventado de um lado só apareceria quando alguém comparasse os dois.
  • Portão 1: validateSpecStructure / validateSpecStructureAs (agent, tool, journey).
  • Portão 2: validateActivation, findCompositionCycle, compositionEdgesAfterApply.
  • scanLeaks(text, { filename }) — segredo, PII, id interno, contexto de turno e identidade que não casa com o arquivo (secret_literal, pii_in_config, internal_id, turn_context, slug_filename_mismatch).
  • toSlug, resolveReference, parseSpecYaml / serializeSpecYaml (KEY_ORDER).
  • PolicySchema, DEFAULT_POLICY, checkAgainstPolicy.
  • Tipos e schemas zod: AgentSpec, ToolSpec, JourneySpec, ToolContract.
  • journeyFlowToGraph, statusInicialDaJornada (dialeto do arquivo → grafo do canvas; jornada criada pelo apply nunca nasce ativa).

O tarball leva só dist/ e o README: as fixtures golden ficam em test/fixtures/ (fora do pacote) e são sintéticas — configuração real de cliente não entra em pacote público. Veja test/fixtures/README.md.

Portes

O código veio de apps/api/src/adk/{spec-gates,reference-resolver,agent-yaml, agent-fields,agent-export}.ts e apps/api/src/tool-registry/tool-contract.ts (hub-v2, origin/staging), e de scripts/validar.mjs (simplafy-clientes, origin/main). Mensagens e path são byte a byte os do original — mudá-los quebraria o mutation check dos dois lados.