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

omk-adaptorch-wpl

v0.95.1

Published

AdaptOrch-native Work Packet Loop (WPL) — state machine, verification layer, and integration bridge for OMK orchestration.

Readme

omk-adaptorch-wpl

Status: Stable (v0.91.0). Wired into open-multi-agent-kit as a runtime dependency. This package implements the AdaptOrch-native Work Packet Loop (WPL) design, an original execution loop whose only work-producing action is AdaptOrch's adaptorch_run tool. See AdaptOrch for the backend product this integrates with; AdaptOrch is still under active development and this integration currently targets its free Start tier.

Design documents

The full design (state machine, verification layer, integration mapping, and the adversarial review that shaped the safety gates below) lives outside this package at .omk/runs/adaptorch-native-loop-algorithm-20260701/:

  • final-part1-core-algorithm.md — Work Packet state machine, termination conditions, cancellation policy
  • final-part2-verification-layer.md — the Outcome Adjudicator (5-state verification)
  • final-part3-integration.md — the projection/bridge between the two

Modules

  • src/types.ts — Work Packet, Dispatch Record, state enums (as string literal unions), on-disk schema types
  • src/state-machine.ts — the packet lifecycle state machine and transition guards
  • src/adaptorch-client.ts — thin typed wrapper around AdaptOrch's 10 MCP tools
  • src/adjudicator.ts + src/adjudicator-registry.ts — the Outcome Adjudicator and its per-kind registry
  • src/loop.ts — the integration layer wiring the state machine, AdaptOrch client, and adjudicator together
  • src/b2c-mapper.ts — B2C (Bridge-to-Code) mapping for patch-apply safety
  • src/b2c-verdict.ts — Verdict card schema for correctness wall decisions
  • src/deep-wall.ts — Deep verification wall for multi-runner evidence gating
  • src/receipt-signature.ts — Cryptographic receipt signing for verification evidence

Integration

The coding-agent consumes this package via:

  • packages/coding-agent/src/core/adaptorch-bridge.ts — advisory-only bridge (default-off, circuit-breaker protected, TTL-cached). Provides getFreshHint (sync, cache-read-only) and requestRefresh (fire-and-forget) for the reasoning router's turn-start path.
  • packages/coding-agent/docs/adaptorch-preview.md — read-first planning pipeline spec.

Safety notes (do not remove without updating the design docs)

  • ESCALATED packets never resume automatically; only an explicit external unblock signal moves them on.
  • The first Dispatch Record of any payload that differs from the last human-approved baseline (an augmented_payload was applied, or a REROUTE changed topology) requires human approval (AWAITING_APPROVAL), unless the loop is explicitly launched in pre-approved-batch mode.
  • Loop-level budgets (max_dispatch_attempts, max_loop_duration, dispatch-call budget) are immutable for a loop instance's lifetime; raising them requires a new instance under the same review.

Preview spec: ../coding-agent/docs/adaptorch-preview.md