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

@agenteer/core

v1.0.0-rc.2

Published

Core runtime, Node primitive, and context store for Agenteer — a debuggable, capability-gated agentic framework.

Readme

@agenteer/core

Core runtime for Agenteer — a debuggable agentic framework where every piece of state (context, evidence, permission decisions) is inspectable, replayable, and bounded by an explicit capability grammar.

This package provides the runtime primitives: the Node type, the runtime loop, the context store (in-memory + file-backed), the event bus, the permission kernel, the manifest schema, and session persistence. It has one runtime dependency on @agenteer/trust for evidence records.

Install

npm install @agenteer/core @agenteer/trust zod

Requires Node ≥ 20.

30-second example

import {
  InMemoryContextStore,
  InMemoryNodeRegistry,
  MemoryEvidenceSink,
  Runtime,
  makeManifest,
  type Node,
} from "@agenteer/core";
import { z } from "zod";

const manifest = makeManifest({
  id: "@example/node-hello",
  name: "hello",
  description: "Says hello.",
  determinism: "deterministic",
  required_actions: [],
});

const registry = new InMemoryNodeRegistry();
registry.register(
  manifest,
  (): Node<{ who: string }, { greeting: string }> => ({
    manifest,
    inputSchema: z.object({ who: z.string() }),
    outputSchema: z.object({ greeting: z.string() }),
    ctx: [],
    model: null,
    async execute(input) {
      return {
        kind: "output",
        value: { greeting: `hello, ${input.original.who}` },
        evidence: { verdict: "pass" },
      };
    },
  }),
);

const runtime = new Runtime({
  registry,
  contextStore: new InMemoryContextStore(),
  evidenceSink: new MemoryEvidenceSink(),
});

const outcome = await runtime.run(
  { manifest_id: manifest.id, input: { who: "world" }, correlation: "root" },
  [`spawn:${manifest.id}`],
);
console.log(outcome.rootResult);

What you get

  • Runtime — the main driver. Authorizes each spawn against a capability envelope, dispatches nodes, applies ctx patches, records evidence.
  • InMemoryContextStore / FileContextStore — content-addressable, immutable context items with slice materialization and staleness propagation.
  • InMemoryNodeRegistry — map of manifest_id → factory. Nodes lookup and instantiate via the registry.
  • Permission kernelauthorizeSpawn, isSubset, intersect, capability grammar parser. Parents can attenuate; children cannot escalate.
  • Manifest schema — Zod-backed schema for NodeManifest with ajv JSON-Schema bridging available via @agenteer/registry.
  • Session persistenceSessionState, SessionRecorder, and recordedAnswerResolver for ask_user / approval_gate pause/resume.
  • Events — typed emitter with node_start, node_complete, evidence_collected, ctx_scope_restricted, etc.
  • ExplainersexplainPermissionDenial and explainManifestIssues turn kernel denials into actionable error text.

Capability grammar

A capability is a string like fs.read:/tmp/**, model:claude-*, tool:gh, or net.http:api.github.com/**. Eleven resource types; glob-scoped; used to gate every spawn and every callAction.

<type>:<scope>

fs.read, fs.write, and fs.delete scopes must be absolute paths or *. shell.exec is scopeless, so use shell.exec: with an empty scope. net.http scopes cover host/path only; the runtime does not encode HTTP method as a separate capability dimension.

Children must declare required capabilities in their manifest. The runtime intersects parent grants with child requirements; the child runs with the intersection. If the intersection is empty or doesn't cover a needed capability, the spawn is denied at authorize time, before any code runs. See capabilities.md for the full grammar.

License

MIT — see LICENSE.