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

@uniscenarios/esmini-runner

v0.1.0-rc.44

Published

Readme

@uniscenarios/esmini-runner

Pinned external execution boundary for esmini 3.6.0. It consumes only the typed EsminiExecutionJob produced by the compatibility bundle builder and returns a browser-safe ExternalRunResult containing execution status, immutable cache identity, structured logs, and opaque artifact handles.

Production jobs must use the Docker invocation profile: no network, read-only root and inputs, an unprivileged user, no Linux capabilities, bounded CPU, memory, processes, runtime, and output. LocalProcessExecutor is explicitly a developer convenience and reports developer-local isolation; it must not be used as production evidence.

The numerical CSV/DAT/OSI outputs and collision log are authoritative external evidence. Frames and video are optional, non-authoritative human evidence.

Install the official pinned binary locally with:

node packages/esmini-runner/scripts/fetch-pinned-esmini.mjs

The helper verifies the upstream archive SHA-256 before extraction. .tools/ must remain untracked. See NOTICE.md for licensing.

For a real local interoperability smoke (not a mocked executor), run scripts/run-pinned-trajectory-smoke.ts with that binary and the straight_500m.xodr fixture from the exact pinned esmini source revision. The script verifies the binary digest, executes a UniScenarios-generated 20-second trajectory at 0.02 s, strictly parses the external CSV, and applies the normal trace-comparison release thresholds. Binaries, source clones, maps, and run outputs stay outside version control.

scripts/run-pinned-capability-probe.ts extends that real-engine check to two actors and requires the collision onset reported through esmini 3.6.0's collision_ids CSV field to agree with the canonical trace within one 0.02 s step. It also makes the traffic-signal boundary executable: the pinned wide CSV has no signal identity/state channel, while the compatibility export promises motion-only replay for signal programs. Signal-edge timing and signal-caused stop-line behavior therefore remain fail-closed; a stopped baked trajectory is not accepted as proof of traffic-signal execution. Native OSC 1.4 execution remains unsupported by this pinned player.