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

@vertikon/wasm-kit

v0.1.0

Published

Developer kit (SDK + CLI + MCP) do wasm-bridge — a IA embarcada WASM do Vertikon (OpenAI-compat, roteia local WASM × nuvem).

Readme

@vertikon/wasm-kit

Kit dev TypeScript/Node do wasm-bridge — a IA embarcada WASM do Vertikon. SDK fino + CLI + servidor MCP.

O bridge é OpenAI-compat e roteia LOCAL (WASM on-device, custo zero) × NUVEM (Vertikon IA) de forma transparente pela regra de domínio — chamar é idêntico nos dois casos. Este pacote é o wrapper fino (fetch nativo + Bearer) do ecossistema.

Drop-in OpenAI: se você já usa o SDK OpenAI, basta trocar a baseURL para https://wasm.vertikon.com.br e usar a WASM_API_KEY como key. Este kit é o atalho fino + CLI + MCP.

Instalar

npm i @vertikon/wasm-kit
# opcional, só para o servidor MCP:
npm i @modelcontextprotocol/sdk

Usar (SDK)

import { WasmClient } from "@vertikon/wasm-kit";

const wasm = new WasmClient({
  baseUrl: "https://wasm.vertikon.com.br", // default
  apiKey: process.env.WASM_API_KEY,        // Authorization: Bearer
});

await wasm.models();                                   // { object, data:[{id,...}] }
await wasm.embeddings({ model: "wasm/embed-small", input: "olá mundo" });
await wasm.chat({ model: "wasm/tiny", messages: [{ role: "user", content: "oi" }] });
await wasm.healthy();                                  // boolean

// forçar inferência local (offline / on-device):
new WasmClient({ offline: true });                     // header X-Vertikon-Offline: 1

Erros de API viram WasmApiError (com status + body).

CLI

export WASM_URL=https://wasm.vertikon.com.br
export WASM_API_KEY=sk-...

vtk-wasm models
vtk-wasm embed --model wasm/embed-small --text "olá mundo"
vtk-wasm chat  --model wasm/tiny --user "resuma isto"
vtk-wasm health
# flags: --url --key --offline

MCP

Servidor stdio com as tools wasm_embed, wasm_chat, wasm_models:

{ "mcpServers": { "vtk-wasm": {
  "command": "vtk-wasm-mcp",
  "env": { "WASM_URL": "https://wasm.vertikon.com.br", "WASM_API_KEY": "sk-..." }
} } }

Contrato

  • POST /v1/embeddings {model, input}{object, data:[{embedding,index}], model, usage}
  • POST /v1/chat/completions {model, messages:[{role,content}]}{choices:[{message:{content}}], usage}
  • GET /v1/models{data:[{id,...}]}
  • GET /healthz (aberto)
  • Auth: Authorization: Bearer <WASM_API_KEYS> nos /v1/*. Fonte canônica dos shapes: service/internal/bridge/bridge.go.

Build / teste

npm install --no-audit --no-fund && npm run build && npm test