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

@gregiteen/ssss-cli

v0.9.0

Published

CLI tools and the reference engine for the Structured Semantic Syntax System

Readme

SSSS — Structured Semantic Syntax System

A database-free, Markdown-first schema and mutation contract for AI-agent state. Turn a running business into a single tradeable file — a festival in a box.

conformance spec OKF

SSSS is the vendor-neutral standard and reference implementation shared by festech.live, ultrachat, and total-recall. It defines:

  • Document primitives — typed Markdown files with YAML frontmatter (workflow, rule, page, assistant, …), validated against a registry, not hand-written code.
  • The Operation Contract (§6) — four envelope types (operation / patch / event / delete) for mutating a vault, with idempotency replay and audit.
  • The Workflow Runtime Contract (§11.8) — workflows own triggers; daemons, crons, and webhooks derive idempotent event/task/run envelopes from the vault.
  • Multilingual semantic runtime (§11.9) — deterministic lexical evidence, injected multilingual embeddings, and runtime rendering with symbolic controls fixed.
  • Portability classification (§5.5) — the keystone: every primitive is structural, tenant_private, or resource_bound, so a vault can be sold without leaking the operator's private data.
  • The .ucw bundle format (§16) and provisioning contract (§17) — package a vault, then export → provision → import it into a fresh tenant, deterministically.

This package, @gregiteen/ssss-cli, is dependency-free: a host needs neither Zod nor a YAML library to be conformant. The reference engine is the validator.

Install

npm install -g @gregiteen/ssss-cli      # the `ssss` command
# or use it as a library:
npm install @gregiteen/ssss-cli

Requires Node 18+. No runtime dependencies.

Start a new project

ssss new my-app --install                # scaffold + install + run the conformance test
ssss new my-app --with-total-recall      # also wire the Total Recall memory OS

Scaffolds a starter vault/, a dependency-free conformance test, and a CLAUDE.md. See ssss help scaffold.

Quick start — the lifecycle

vault ──export──▶ .ucw bundle ──provision──▶ envelope plan ──import──▶ new vault
        (§16, pure)            (§17, params + links)        (§6, idempotent)
# 1. Package a vault as a sellable bundle (drops tenant-private data)
ssss export ./my-vault --profile sale --out festival.ucw.json

# 2. Inspect / verify it
ssss inspect  festival.ucw.json --files
ssss validate festival.ucw.json

# 3. Stand up a fresh tenant from it
ssss import festival.ucw.json --vault ./new-tenant \
  --param business_name="Acme Fest" --param domain=acme.live

# Re-running import commits nothing — it is idempotent.

Commands

| Command | Purpose | |---------|---------| | ssss new <dir> | Scaffold a new SSSS project (--with-total-recall, --install). | | ssss export <vault> | Package a vault into a .ucw bundle (§16). Pure & deterministic. | | ssss validate <bundle> | Check a bundle against the schema + portability rules. | | ssss inspect <bundle> | Human-readable summary (manifest, inventory, params, steps). | | ssss provision <bundle> | Plan an install: params + link integrity → envelopes (§17). | | ssss import <bundle> | Replay a bundle/plan into a vault via the engine (idempotent). | | ssss semantic <vault> | Build or query a deterministic, privacy-safe semantic index (§11.9). | | ssss autolink [dir] | Generate OKF wiki-links across a vault. | | ssss conformance | Run the canonical conformance suite (§12). | | ssss help [topic] | Local docs: runtime, portability, bundle, provisioning, leases, … |

Run ssss <command> --help for flags, or ssss help <topic> for concepts.

Use as a library

import { createEngine } from '@gregiteen/ssss-cli/engine';
import { exportBundle, validateBundle, provisionBundle, importBundle } from '@gregiteen/ssss-cli/bundle';
import { planWorkflowTrigger } from '@gregiteen/ssss-cli/runtime';
import { buildSemanticIndex, searchSemanticIndex, renderSemanticRecord } from '@gregiteen/ssss-cli/semantic';

const bundle = exportBundle('./my-vault', { profile: 'sale', name: 'Festival in a Box' });
const { valid, errors } = validateBundle(bundle);

const engine = createEngine();
const plan = provisionBundle(bundle, { parameters: { domain: 'acme.live' }, workspaceId: 'ws-1' });
importBundle(plan.plan, './new-tenant', engine);

const workflowContent = `---
type: workflow
name: "Daily Digest"
---

1. Gather messages.
2. Summarize.
3. Send digest.
`;
const runtimePlan = planWorkflowTrigger({
  workflowPath: 'workflows/daily-digest/WORKFLOW.md',
  workflowContent,
  workspaceId: 'ws-1',
  trigger: { type: 'cron', id: 'daily-0800', cron: '0 8 * * *' },
  scheduledFor: '2026-07-02T14:00:00.000Z',
});

const index = buildSemanticIndex('./my-vault');
const matches = searchSemanticIndex(index, 'política de reembolsos');
const rendered = await renderSemanticRecord(matches[0].document, { language: 'es', render: renderer });

Exports: @gregiteen/ssss-cli / @gregiteen/ssss-cli/engine (Operation Contract engine), @gregiteen/ssss-cli/bundle (export/provision/import), @gregiteen/ssss-cli/registry, @gregiteen/ssss-cli/runtime, @gregiteen/ssss-cli/semantic, @gregiteen/ssss-cli/frontmatter.

Canonical content is authored once in any language. Multilingual embedding and render adapters handle cross-language retrieval and presentation at runtime; primitive IDs, field IDs, enum codes, permissions, paths, hashes, and relations never change.

Portability — why a vault is safe to sell

| Class | Meaning | In a sale export? | |-------|---------|---------------------| | structural | The sellable business model (workflow, rule, page, …). | ✅ shipped | | resource_bound | Needs a real resource bound at provision (domain, phone_number). | ✅ shipped (as a parameter/step) | | tenant_private | The operator's private data (task, customer records). | ❌ dropped |

template and sale exports MUST drop every tenant_private file. The reference bundle proves it — see ssss help portability.

Conformance

A host MUST NOT claim SSSS conformance without passing the suite in conformance/:

ssss conformance            # structural + registry validation
ssss conformance --engine   # + replay all fixtures + round-trip the reference bundle
npm test                    # == ssss conformance --engine

Repository layout

docs/ssss-spec.md          The normative specification (v0.9 draft).
docs/help/                 Topic docs surfaced by `ssss help`.
registry/core.json         15 document + 5 contract primitives; semantic, bundle & provisioning schemas.
registry/extensions/       Application extension registries (e.g. festech).
src/engine.mjs             Operation Contract engine (§6).
src/runtime.mjs            Workflow trigger → event/task/run envelope planning (§11.8).
src/semantic.mjs           Multilingual semantic retrieval + runtime rendering (§11.9).
src/bundle.mjs             export / validate / provision / import (§16–§17).
src/registry.mjs           Registry-driven type + portability resolution.
src/frontmatter.mjs        Zero-dependency YAML frontmatter.
scripts/ssss.mjs           The `ssss` CLI dispatcher.
conformance/               Canonical fixtures + reference bundle.
skills/ssss/               Packaged SSSS system skill and dependency-free validator.

License

ISC © Greg Iteen. See LICENSE.