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

@moolam/edge-agent

v1.1.0

Published

Internal component of Sutra SDK — applications should install sutra-sdk. The Edge Harness. Offline-first autonomous agent runtime for local SLMs (Phi-3, Gemma, quantized GGUF/ONNX) with durable friction telemetry and on-device vector memory.

Readme

@moolam/edge-agent

The offline-first on-device host. EdgeAgent runs the full cognitive loop against a local SLM and a local vector store, with zero connectivity, indefinitely. It is not a degraded cache of the cloud: it is a peer replica that acts independently and converges through CRDT sync when connectivity returns (ADR 0002).

Architecture

| File | Responsibility | |---|---| | src/edge_agent.ts | The host facade: agentTurn() composes local routing, prompt assembly, SLM inference, friction folding, and memory writes | | src/slm_runtime.ts | The pluggable SLM seam: OpenAI-compatible localhost adapter shipped; llama.cpp, ONNX Runtime Mobile, AICore, and MLX adapters are roadmap Stage 2 | | src/local_vector_db.ts | LocalVectorDb: SQLite-backed vector memory (Float32 BLOBs, exact cosine, kind-aware decay, corrections never evicted) behind the StorageDriver contract |

Friction telemetry comes from @moolam/telemetry; sync comes from @moolam/sync-protocol. Routing on-device is a greedy simplification of the cloud task router; on reconnect the cloud's LWW registers win without conflict (PRD ATR-06).

Public API

EdgeAgent, AgentReply, LocalVectorDb, the SLM runtime interface and adapters, exported from src/index.ts.

Quick start

import { EdgeAgent } from "@moolam/edge-agent";

const agent = new EdgeAgent({
  subjectId: "subject-1",
  deviceId: "device-a",
  runtime: slmRuntime,        // any SlmRuntime adapter
  storage: storageDriver,     // any StorageDriver (SQLite binding)
  profile,                    // track, language, age band
  // transport omitted = permanently-offline sovereign mode
});
await agent.initialize();

const reply = await agent.agentTurn("Explain this step to me.", frictionSample);
// works with the network cable cut; reply.servedLocally === true

Contributing notes

  • Every feature must answer "what does this do offline" at design time.
  • Missing or corrupt on-disk weights must throw typed SlmRuntimeInitError (missing_weights / corrupt_weights) — never crash-loop or fabricate. See LocalWeightSlmRuntime and the drill map in docs/protocol/DEGRADATION-DRILL-CROSSREF.md.
  • Memory store changes must preserve parity with the cloud memory_graph.py semantics (same decay, same kinds), or document why the divergence is substrate-specific.
  • Performance budgets: first token ≤ 1.5s p95 on mid-range Android (NFR-01).

Examples

examples/offline-edge/ runs a full turn with no network; examples/memory/ exercises LocalVectorDb directly.

Tests

Currently covered through the examples and the protocol smoke tests; per-package unit tests are a welcome contribution (see CONTRIBUTING.md).