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

@aimount/engine

v0.1.0-alpha.0

Published

Provider-neutral execution engine shell for aimount runtimes

Readme

@aimount/engine

@aimount/engine is the provider-neutral execution core for aimount runtimes.

For the normative package contract, see ARCH.md.

Role

This package owns execution semantics that are independent of any specific provider framework.

Owns

  • provider-neutral provider event, request, and port types
  • continuation reconstruction and replay eligibility
  • deterministic context-window selection
  • internal runtime-event mapping and stream-state finalization
  • the inline execution driver that emits canonical runtime events and final completion state

Does not own

  • HTTP or gRPC transport publishing
  • provider-framework adapters
  • host-specific request wiring
  • proxy-specific behavior
  • persistence, queues, leases, and durable worker behavior
  • framework-specific message conversion or tool mapping

Dependency direction

@aimount/engine depends on @aimount/core for canonical runtime model contracts. Adapter packages such as @aimount/engine-aisdk depend on @aimount/engine, while compatibility packages such as @aimount/runtime stay above the core-owned model layer for protocol, wire, and codec entrypoints.

Runtime API relation

The engine executes semantics that surface through the canonical RuntimeApi, but it does so through provider-neutral inputs and outputs rather than transport or provider SDK types.

Tool execution relation

The engine owns canonical tool lifecycle semantics, but concrete provider bindings stay in adapter packages above this layer.

Status

Experimental execution core implemented in the aw worktree extraction branch.

The package remains experimental while the extraction and cloud cutover are in progress.

Current public surface

  • provider-neutral provider event types
  • engine request and provider port types
  • continuation and context-window helpers
  • inline execution via executeEngineInline(...)

Current implementation boundary

This package intentionally keeps provider-framework code out of the base layer. AI SDK conversion, streamText(...), and AI SDK chunk normalization live in @aimount/engine-aisdk instead.