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

@forgegraph/runtime

v0.4.0

Published

Effect runtime for ForgeGraph applications: engine, storage adapters (D1, DynamoDB, PostgreSQL, memory), hosts (Cloudflare, AWS, Node), workflows, schedules, realtime, governance and telemetry.

Readme

@forgegraph/runtime

The Effect runtime for a ForgeGraph application bundle. One bundle (app.json, produced by forgec build) plus your impl/ functions run unchanged on Cloudflare Workers, AWS Lambda and Node — the adapters differ, the observable behaviour does not.

Stability: stable-candidate. The engine, host and adapter entry points below are the supported surface; anything not documented here may change in a minor release before 1.0.

npm install @forgegraph/runtime

Entry points

| import | what | |---|---| | @forgegraph/runtime | Engine, Model, createHttpHandler, jwtAuth, devHeaderAuth, errors, codecs, telemetry, gatekeeper, suppression | | @forgegraph/runtime/node | createNodeHost — Fetch server, realtime hub, durable sweep, graceful drain | | @forgegraph/runtime/cloudflare | Workers entrypoint, Workflows binding, Durable Object realtime | | @forgegraph/runtime/aws | Lambda handler, Step Functions driver, API Gateway WebSocket | | @forgegraph/runtime/d1, /dynamodb, /postgres, /memory | storage adapters | | @forgegraph/runtime/r2, /s3, /memory-objects | object stores | | @forgegraph/runtime/compose | composeRuntime — wire an engine without a host |

Minimal Node host

import { createNodeHost } from "@forgegraph/runtime/node";
import { createPostgresStorage } from "@forgegraph/runtime/postgres";
import { jwtAuth, Model, type AppBundle } from "@forgegraph/runtime";
import bundle from "./generated/app.json" with { type: "json" };
import { functions, externals } from "./impl/index.js";

const app = bundle as unknown as AppBundle;
const host = createNodeHost({
  bundle: app,
  store: createPostgresStorage(pool, new Model(app)),
  functions,
  externals,
  auth: jwtAuth({ issuer, audience, secret, claims: { tenant: "tid", actor: "sub" } }),
  cursorSecret: process.env.CURSOR_SECRET!,
});
await host.listen(8080);

The host refuses to start without an authentication host. For local development set FORGE_AUTH=dev-headers, which trusts x-forge-tenant / x-forge-actor verbatim and logs a warning on every boot. Never enable it where untrusted callers can reach the process.

Documentation

Getting started · Portable profile · Operations

Apache-2.0

Blob finalization hashes the sealed copy and checks its byte count after copying. Each contender uses a fresh private object key, so a losing metadata commit cannot replace a winner's bytes. The hidden sealedGeneration field stores a versioned forge-sealed/1 object token plus provider generation; readers still support legacy generation-only keys. Upgrade readers before writers; older runtime versions cannot read the new object-token format. Failed finalizations may leave unreferenced private objects for lifecycle cleanup. This is local race coverage, not live R2/S3 certification.

Opt-in Foundation application adapters

The runtime package ships experimental application adapters as explicit subpath exports:

import { withFoundationProduction } from "@forgegraph/runtime/foundation/apps/levelforge";
import { assessChangeset } from "@forgegraph/runtime/foundation/apps/forgegraph";

Additional subpaths are bob, kanbanger, latchflow, and stream-conductor. They accept structural application ports. Bob and KanBanger accept an explicit Effect runner; the other adapters use the runtime's own Effect dependency internally. They do not install or enable an application. Compile the corresponding examples/foundation/apps/<app> schema into the application's Foundation deployment and supply authenticated tenant context and trusted bindings. Each example documents its integration seam and recovery boundaries. These optional adapters preserve application vocabulary; they are not new generic Foundation packages.

pnpm foundation:distribution unpacks the real pnpm pack tarball into an external temporary consumer and checks all six JavaScript exports and TypeScript declarations. It rejects unresolved workspace dependency protocols.