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

@zana-ai/core

v0.1.5

Published

Zana engine — multi-agent orchestration, scheduling, persistence, and module system. Used by @zana-ai/mcp.

Readme

@zana-ai/core

Foundational engine for Zana — a multi-agent orchestrator for Claude Code.

This package owns the cross-cutting primitives every other Zana package builds on:

  • agents — profile loading, lifecycle, headless spawn, hooks
  • events — append-only event bus + replayable channels
  • project — workspace-context singleton (tenant isolation)
  • modules — pluggable capability registration
  • persistence — content-addressed artifact store + checkpoints
  • daemon — long-lived process entry point (bin/daemon.ts)
  • host — process bootstrap, signal handling, IPC plumbing
  • guardrails — policy gates shared across the runtime

Install

npm install @zana-ai/core

Public surface

import {
  agents,
  events,
  project,
  modules,
  persistence,
} from "@zana-ai/core";

project.workspaceContext.init(process.cwd());
const bus = events.bus;

The package uses lazy require getters in its facade to break what would otherwise be circular dependencies between sibling packages. Always import from the top-level entry, not from dist/<subpath> directly.

Workspace context — tenant isolation

Every project-local path (tickets, runs, checkpoints, scheduler, events, artifacts) resolves through project.workspaceContext.getProjectPaths(). Adding a new project-local directory means adding it to BOTH the singleton branch and the createForWorkspace factory in project/workspace-context.ts, and consuming it via the workspace-context lookup — never by joining paths from the workspace root in the calling module.

Tenant-isolated writes (CAS artifacts, kind: "deliberation" checkpoints) must refuse the global ~/.zana/ fallback. Use WorkspaceNotInitializedError to refuse rather than silently writing to a host-shared directory.

Build & test

npm run -w @zana-ai/core build
cd packages/core && npx vitest run

Built-in profiles ship under packages/core/profiles/; user profiles live in ~/.zana/profiles/.

See also