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/app-kit

v0.1.0

Published

Kit público para construir apps do Hub da Simplafy — tokens do design system, componentes base, <Brand/> e a ponte postMessage com o host.

Readme

@simplafy-tec/app-kit

Kit público para construir apps do Hub da Simplafy. Sem token, sem registro privado:

npm i @simplafy-tec/app-kit

O caminho normal é começar pelo esqueleto, não pelo pacote:

npx create-simplafy-app meu-app   # ou: adk init app meu-app
cd meu-app && npm install
adk dev                            # Vite (HMR) + Hub shell local em 127.0.0.1

O que vem

| Export | O que é | | ------------------------------------------------------------------------- | ------------------------------------------------------------------------------ | | tokens.css (@simplafy-tec/app-kit/tokens.css) | Tokens do design system: --color-*, --font-*, --radius-*, claro e escuro | | simplafyAppPreset (@simplafy-tec/app-kit/tailwind-preset) | Preset Tailwind com a mesma paleta | | Button, Badge, Input, Select, Switch, Card, Dialog, Toast | Componentes base | | <Brand/> | O único ponto de logo da Simplafy | | useHost() | Lado app da ponte: toast, dialog, navigate, theme | | HostShell | Lado host: embute o app em <iframe> e renderiza o que ele pediu | | applyTheme, color, font, radius | Utilitários de tema e token |

Storybook público com todos os componentes: pnpm build-storybook.

Regras de aderência

O adk build (e o apply do Hub, com a MESMA função) reprovam com o código ui_adherence:

  • cor literal — #22c55e, rgb(...), oklch(...) no seu código. Use var(--color-*).
  • fonte fora do token — font-family: "Comic Sans MS". Use var(--font-sans).
  • logo fora de <Brand/> — <img>/SVG de marca solto.

A ponte

O app roda num <iframe>. Toda troca com o Hub é um envelope versionado { v: 1, type, payload }, validado por zod dos dois lados, com a origem conferida por allowlist exata. Mensagem fora do contrato é descartada em silêncio — nunca lança.

Nada de autoridade trafega aqui: organização, usuária, papel e token vêm do servidor para o host, jamais de um postMessage.

Fronteira

Este pacote não contém componente exclusivo do produto (estúdio de agente, console de BI, inbox, jornada) nem depende de @simplafy-tec/ui. A auditoria do tarball roda no CI.