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

@galaxie-ai/core

v0.1.0

Published

Runtime and framework-neutral contracts for browser agents.

Readme

@galaxie-ai/core

Framework-neutral contracts and the host runtime for reviewed, bundled browser agents. Core owns lifecycle, policy, budgets, interactions, capability dispatch, optional recovery and allowlisted OpenTelemetry spans. It calls the OpenTelemetry API; the host registers the SDK and exporter.

Install

This is a private workspace package, not a published npm release. From this repository's root, use Node 24 and pnpm 11, run pnpm install --frozen-lockfile, then pnpm build. Workspace consumers declare @galaxie-ai/core as workspace:*. Peer requirements are in package.json.

Entry points

@galaxie-ai/core exports runtime APIs and framework-neutral contracts. It uses no unguarded browser globals and can import and run without page APIs. Optional storage persistence and development page warnings keep their feature guards.

@galaxie-ai/core/browser exports acquireOwnership, watchInvalidation, Ownership, OwnershipLostReason, OwnershipOptions, OwnershipResult, InvalidationOptions and InvalidationWatcher. Ownership requires Web Locks and BroadcastChannel; invalidation requires BroadcastChannel and also works in a Worker.

Moving these functions and types out of the main entry is a breaking change to the public API of this package, which has not been published. Update host imports:

import { acquireOwnership, watchInvalidation } from '@galaxie-ai/core/browser';

Minimal host setup

import { createRuntime } from '@galaxie-ai/core';
import { createLangGraphAdapter } from '@galaxie-ai/adapter-langgraph';

const runtime = createRuntime({
  appId: 'lesson-app',
  executors: [createLangGraphAdapter()],
});
// Create and prepare instances, then handle their snapshots and interactions.
// At host teardown:
await runtime.dispose();

Choose appId and each instance's principalScope as strings of 1 to 128 characters from A-Z a-z 0-9 . _ : -. Core checks appId in createRuntime and principalScope first in runtime.create, before creating instance state or calling hooks. Invalid values fail with fixed invalid errors. Ownership, invalidation and IndexedDB storage use the same rule. Derive the principal from trusted host session context and use the same pair for runtime and storage.

The adapter example supplies a graph and an agent definition. Hosts bind capabilities and model routes explicitly; direct agent platform access bypasses those controls.

See coding guidance, runtime contracts, the mandatory baseline and conformance coverage. Code is Apache-2.0 (see LICENSE).

Decision roles

Declare a bounded role with models: { triage: { modality: 'decision' } }. Its host route lists only descriptors with modality: 'decision'; preparation rejects mixed modalities. Decisions reuse readiness, download and destination consent, per-call credentials, sticky run labels, reservations and settlement. Default private-user policy still permits only in-browser calls.

Core exports DecisionRequest, DecisionQuestion, DecisionAnswer, DecisionResult, DecisionModel, DecisionModelOptions and DecisionProvider. validateDecisionRequest and validateDecisionAnswers return detached immutable values or fixed, content-free invalid errors. Requests contain JSON state and 1–16 named boolean, choice (single or multiple), or integer score questions. Scores have 2–10 inclusive levels. Answers must match every question exactly; optional confidence and complete probability distributions are finite in [0, 1]. Each categorical distribution sums to 1 within 0.000001, including each separate multi-select yes/no pair. No confidence is inferred from probabilities.

The LangGraph decision entry uses the active run's RunRequest.payload boundary for the whole request and answer, retaining the existing payloadBytes limit and budget_exceeded outcome. Direct shape validators alone do not apply a run budget or destination policy. Decision providers receive { signal, maxTokens, repair? } and return { answers, usage?, raw? }; a dedicated forward pass reports input tokens and zero output tokens. Missing or invalid usage and failed calls charge the reservation. There is no new accounting unit. raw?: string is unvalidated generated text used only for output checks and bounded repair; it is never returned to callers or stored. repair?: { attempt, reply } carries the one-based attempt and previous raw reply, without validator text. Each repair obtains a new ordinary lease under the route's repairAttempts (default zero) and shared run repair budget. Completed invalid answers settle reported usage; provider failures charge the reservation. See ADR-0028. Confidence gates and dedicated decision models remain unimplemented.

Materialized pending surfaces

Core depends on @galaxie-ai/ui-protocol through its public root; its existing peers remain unchanged. Hosts can bind ui.catalogs by catalog ID alongside ui.surfaces and registered component actions. Core validates materialized interrupt records before publication and again on restore, using the run's payload and UI-element limits and the whole-surface URL/private-value policy. Missing bindings fail closed.

materializeSurface({ binding, catalog, previous?, messages, limits, isAllowedUrl }) wraps the protocol reducer for trusted node code. parseSurfaceRecord checks the plain JSON record shape, and pendingFromSurface creates a detached, frozen legacy projection plus surface. These helpers do not authorize publication. surfaceFromRequest(request, catalogId) maps a representable legacy request to a single root component; props containing id or component return undefined. Legacy requests still follow their original validation path.

Surface events additionally supply surfaceAction: { revision, componentId, dataModel }. Core checks the committed revision, registered action and payload, and changes only to paths related to a component's data binding. Changed string leaves receive private-user before inbox acceptance. Only { action, payload } resumes the node. See the runtime contract for checkpoint, restore and replay limits.