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

@loop-engine/runtime-routes

v1.0.0-rc.1

Published

Route handler factories for the RT-01 frozen Loop Engine runtime API. Mounted by the OSS self-host app (`apps/loop-engine-runtime`).

Downloads

104

Readme

@loop-engine/runtime-routes

Route handler factories for the RT-01 frozen Loop Engine runtime API surface, consumed by the OSS self-host app apps/loop-engine-runtime.

What's inside

| Factory | Mounts | | --- | --- | | createRunDetailHandler(ctx) | GET /api/v1/runs/{id} | | createRunHistoryHandler(ctx) | GET /api/v1/runs/{id}/history | | createRunEvidenceHandler(ctx) | GET /api/v1/runs/{id}/evidence | | createRunTimelineHandler(ctx) | GET /api/v1/runs/{id}/timeline | | createRunReplaySummaryHandler(ctx) | GET /api/v1/runs/{id}/replay-summary | | createMetadataConnectionsHandler() | GET /api/v1/metadata/connections |

Each factory takes the RuntimeContext exported from @loop-engine/runtime-core (auth adapter, entitlements adapter, trace store, trace repository, traceReadEnabled flag) and returns a Web standard (request, ctx) => Promise<Response> handler. The OSS app re-exports each as GET from its Next.js Route Handler files.

Run-scoped routes go through withPersistedRunRead, which enforces the frozen RT-01 contract:

  1. LOOP_TRACE_ENABLED gate (503 when disabled).
  2. AuthAdapter.authenticate (401 on miss).
  3. assertRuntimeAllowed on the entitlements snapshot (403 on tier 0).
  4. In-process sliding-window rate limit per tenant (429 on overrun).
  5. traceRepository.getRunSummary → 404 if missing.
  6. Build response and serialize as JSON.

Tests

pnpm --filter @loop-engine/runtime-routes test

Tests use MemoryAuthAdapter, MemoryEntitlementsAdapter, and an in-memory trace store/repository — no Postgres required.

License

Apache-2.0. See LICENSE.