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

@belto_inc/slyos

v0.1.3

Published

Belto SlyOS SDK: local-first AI infrastructure for apps.

Readme

@belto_inc/slyos

Belto SlyOS SDK for local-first and hybrid AI infrastructure.

npm install @belto_inc/slyos
import { Belto } from "@belto_inc/slyos";

const belto = new Belto({
  apiKey: process.env.BELTO_API_KEY!,
  mode: "local-first"
});

await belto.initialize();

const response = await belto.chat({
  messages: [{ role: "user", content: "Summarize this document" }],
  rag: true
});

console.log(response.text);
console.log(response.route);

By default the SDK runs in local-first mode and auto-detects real local runtimes:

  • Node/Electron/dev machines: AutoLocalRuntimeAdapter uses Ollama when http://127.0.0.1:11434 is available.
  • Browsers: AutoLocalRuntimeAdapter uses WebLLM when WebGPU and @mlc-ai/web-llm are available.
  • Cloud fallback: SmartRoute uses the Belto API and Amazon Bedrock only when local is unavailable, blocked by policy, or the request is better suited to cloud.

For the simplest local test:

ollama serve
ollama pull llama3.2:3b

Then run the SDK with mode: "local-first". SmartRoute will report a local route for simple prompts when the local model is available.

Edge RAG is also enabled by default:

await belto.addDocuments({
  storageStrategy: "edge-first",
  maxEdgeStorageBytes: 25 * 1024 * 1024,
  cloudSpillover: true,
  knowledgeBaseId: "kb_optional_for_cloud_spillover",
  documents: [{ filename: "faq.txt", rawText: "Belto keeps this context on device first." }]
});

Node/Electron stores edge chunks under ~/.belto-slyos/rag; browsers store them in IndexedDB.