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

@rayspec/record-runtime

v1.7.0

Published

The generic Tier-B submit-ingress capability (record_input) — authenticated JSON records in, a durable workflow trigger out. Product-neutral; mirrors @rayspec/audio-runtime's manifest/mount/event pattern.

Readme

@rayspec/record-runtime

The generic Tier-B submit-ingress capability (record_input): one authenticated POST /records/{record_id}/submit route that turns a JSON business record into the record_input.record_submitted workflow trigger event. Product-neutral by law — the record's fields are arbitrary product DATA (never instructions — the trust boundary); this package carries zero product vocabulary (enforced by manifest.test.ts + deployed-surface.test.ts).

The durability recipe (the audio pattern, adopted)

  • Deterministic tenant-scoped event id${tenantId}:${record_id}.
  • Idempotent re-submit re-emits — persist first (atomic upsert on the tenant-prefixed record_ref unique), then emit on EVERY successful submit; the tenant-bound dispatcher dedups by the descriptor-derived key record_id:<id> (idempotent single-flight — client retry = redelivery).
  • Per-tenant capability-store keyingrecord_ref embeds the server-derived tenant, so two tenants' identical record_id never collide (NOT the declared-store global-key caveat class).
  • Different payload, same key → loud 409 (record_conflict, canonical-JSON payload hash) — never a silent dedup onto different data; the stored payload is authoritative (re-read on emit).

The payload contract (manifest-stated, gate-pinned)

Submitted business fields MERGE top-level into the trigger payload alongside the fixed envelope (record_id · tenant_id · source_capability) — that is what makes them reachable by store_write { event: <field> } sources. The envelope keys are therefore RESERVED in a submission body (422), the canonical-JSON serialization is capped at 64 KiB (413), and the seam adapter (@rayspec/record-workflow-bridge) stamps the envelope LAST (envelope wins).

Composition

composeProductDeploy mounts this capability iff the Product-YAML doc declares record_input (the conditional-mount law; audio stays unconditional), wiring the submit route to the same tenant-bound WorkflowEventDispatcher behind the bridge's fail-closed cross-tenant sink (403 record_event_rejected, zero enqueue).