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

spielos

v10.3.3

Published

SpielOS: a clean durable Goal runtime with declarative Departments, evidence, and approvals.

Readme

SpielOS

The operating system for AI-run companies.

spielos.xyz · one durable Goal loop, Agent-owned Departments, approvals, evidence, and memory — all local, all on disk.

GOAL → OBSERVE → DECIDE → ACT → EVALUATE

Turn business intent into measurable Goals. The Director Agent (in OpenCode or Codex) owns the conversation; SpielOS owns the durable loop behind it: every run, work order, approval, evidence record, and memory item is persisted in a local SQLite database — never lost when a chat session ends.

Install

One line with pipx (requires Python 3.11+):

pipx install spielos && spielos init --dir my-company -y

One line with Homebrew:

brew install shayanspiel/spielos/spielos && spielos init --dir my-company -y

One line with npm (thin launcher; needs the Python package too):

npm i -g spielos && pipx install spielos && spielos init --dir my-company -y

One line with curl:

curl -fsSL https://raw.githubusercontent.com/ShayanSpiel/SpielOS/main/install.sh | sh

One line with curl and a Department bundle (local folder or git URL):

curl -fsSL https://raw.githubusercontent.com/ShayanSpiel/SpielOS/main/install.sh | sh -s -- --bundle /path/to/bundle-folder

--bundle installs the product, creates the home, and imports the Department in one step, then prints your next steps. Bundle folders come from company export (a complete repository with a README that onboards you through OpenCode, Codex, or Claude Code with a paste-prompt block).

The chosen folder becomes a self-contained SpielOS home: the runtime spine, Director agent + host adapters for OpenCode, Codex, and Claude Code, and empty private state. The spielos command itself is a global CLI — your company data always lives in the folder you chose.

Talk to your Director

cd my-company
opencode    # or: codex

In OpenCode: run /agents, select the Director agent, and talk to it — it already sees your company state.

In Codex: talk to the Director agent — it already sees your company state.

No manual probing, no status commands to start: the host injects a fresh, read-only company projection into every model request.

Update

pipx upgrade spielos && spielos update --dir /path/to/your/home

update refreshes only the vendored spine and host adapters; your private .spielos/ state, owner profile, memory, and user Departments are always preserved. Stale files from older releases are pruned so the home matches a fresh install exactly.

What's inside

| Concept | What it is | |---|---| | GoalRuntime | The one durable control loop: observe, decide, act, evaluate | | Goal | A measurable outcome with an owner, metric, and target | | Department | A declarative, Agent-owned capability package | | Workflow | Ordered steps with declared evidence and approval keys | | Agent | Performs claimed work orders through a Host | | Evidence | Immutable proof attached to Goals and Runs | | Memory | Three scopes: owner profile, workflow learning, strategy learning | | Approval | Explicit owner keys — external actions always park first |

Fresh homes start with zero Departments — add clean declarative packages only when their Goal, Workflow, Agent, Evidence, and approval contracts are ready. Shareable Departments travel as bundle repositories (company export / company import); see the bundle walkthrough.

Executor identity is enforced: a WorkOrder executes only for its declared agent (exact string, no aliases), claims are claim-then-complete, and work for an agent that is neither installed, nor the goal owner, nor declared by the owning Department is refused upfront and escalated to the owner instead.

Memory retrieval is topology-aware: a Goal's relevant memory carries the strategy claims of Goals it is structurally related to (same owner and metric, parent, child, or supports edge), parked asks append the workflow or goal-relevant learning they should build on, and every WorkOrder brief carries that bounded memory list so the next execution differs from the last — memory is causal, not decorative. Direct-work lessons are goal-keyed: a lesson learned completing a direct order (workflow_id NULL) reaches future direct orders of that same Goal. Strategy memory stays selective — completing a goal writes no new strategy claims; owners and evidence-backed host distillation are the only strategy writers, operational lessons are the only per-completion writes, and stale claims retire with memory retire without losing their evidence. Approvals acknowledge their answered asks, and unknown comparison operators raise instead of silently failing closed.

Useful commands:

spielos status
spielos overview
spielos context
spielos memory summary
spielos memory retire <memory_id>
spielos profile list
spielos notifications list
spielos runner tick

Development

git clone https://github.com/ShayanSpiel/SpielOS.git
cd SpielOS
PYTHONDONTWRITEBYTECODE=1 python3 -B -m unittest company.tests.test_clean_core_acceptance