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

sutra-sdk

v1.1.0

Published

Sutra SDK — the public npm entry point. Re-exports the stable APIs of contracts, cognitive-core, runtime, telemetry, sync-protocol, and edge-agent so applications import one package.

Readme

sutra-sdk

The one public entry point. Applications import from here; internal package layout may shift between minor versions while this surface stays stable and semver-governed.

import { CognitiveCore } from "sutra-sdk";

Architecture

A re-export barrel with no logic of its own. Layering (each layer depends only on layers above it):

| Layer | Package | Re-exported surface | |---|---|---| | Contracts | @moolam/contracts | All cognitive and runtime interfaces | | Protocol | @moolam/sync-protocol | CognitiveState, CRDT resolver, HLC clock, sync engine, schemas | | Core | @moolam/cognitive-core | CognitiveCore, CognitiveBindings, AgentProfile | | Runtime | @moolam/runtime | RuntimeHost, InProcessScheduler, InProcessEventBus | | Telemetry | @moolam/telemetry | CognitiveTelemetryCollector, event and sample types | | Edge | @moolam/edge-agent | EdgeAgent, LocalVectorDb, SLM runtime adapters |

Public API

Everything exported from src/index.ts. If a symbol is not exported here, treat it as internal even if its package exposes it.

Quick start

Scaffold a companion outside the monorepo (create-sutra), then:

import { CognitiveCore } from "sutra-sdk";

Full walkthrough: docs/sdk/implementor-quickstart.md.
Conformance stub + binding certification: docs/sdk/conformance-stub-guide.md, docs/sdk/binding-certification-guide.md. Binding recommendations per profession: domains/*/interfaces.md.

Contributing notes

  • Additions here are additions to the public contract; removals are breaking changes. Prefer exporting from the owning package first and promoting to the SDK once stable.
  • Keep this package logic-free. Helpers belong in the owning layer.

Examples

Every script in examples/ imports exclusively from sutra-sdk; they are the living documentation of this surface.