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

@open-everywhere/core

v0.7.0

Published

Open Everywhere core — the portable, host-agnostic agent runtime: access and approvals, identity, memory, spend, routines, webhooks, connectors, the audit chain and the `oe` roster build.

Readme

@open-everywhere/core

The portable, host-agnostic agent runtime behind Open Everywhere.

Part of Open Everywhere — an open, self-hostable autonomous teammate you tag where your team works. This package is the runtime every deployment loads.

Core owns the parts that do not depend on a chat platform or a host:

  • access and approvals — the tool consequence table, window and work-grant planes, approval cards
  • identity — principals, seats and the member planes
  • memory — per-team stores over git, SQLite, Postgres, GitHub or Notion
  • spend — the ingress spend gate and the cost reports
  • routines and webhooks — scheduled and event-driven wakes
  • connectors — host-side connections whose token is attached outside the sandbox
  • the audit chain — one row per decision, and the control-plane read route over it
  • the oe roster build — oe build compiles roster.config.ts into the generated tables

Each chat surface ships as a separate @open-everywhere/provider-* package, and core's registries refuse a provider this deployment has not selected. The boundary is a vendor-coupling one, checked per provider by packages/core/scripts/boundary-test.ts: it names one or more vendor fingerprint strings — a host literal, a credential env key or a signature header — then asserts that at least one of them appears under that provider's package, and that every one of them is absent from packages/core/agent.

It is not a rule that core never mentions a platform, and some vendor surface is core's on purpose: the source-control plane calls api.github.com from core, and the spend plane renders Slack's own shortcodes.

Install

npm i @open-everywhere/core [email protected]
npx oe-eve-patch

Both commands are required. Core refuses to boot on an unpatched eve. It reads one runtime marker for each live patch part before the first wake is served, and it throws when a marker is missing. A registry eve carries no patch, so npx oe-eve-patch applies the copy in this tarball. The applier is idempotent: a second run on a patched tree changes nothing and exits 0. An eve that holds an older Open Everywhere patch under the same pin is restored from its registry tarball (npm pack) and patched again, so an upgrade needs no manual reinstall of eve.

eve is a peer dependency, and the version above is the pin this package declares as peerDependencies.eve. Install that exact version yourself. npm can still nest a second eve for a package that asks for another version. oe-eve-patch patches only the copy at <project root>/node_modules/eve, and the boot check reads only the copy core itself resolves. A nested copy is therefore neither patched nor checked, so one resolved, pinned eve is your own step — run npm ls eve and confirm it prints one version. Node 24 or newer.

Bins

  • oe — the roster build and the operator commands
  • oe-eve-patch — applies the eve patch this version pins, which a registry install of eve does not carry. It is a required install step, not an optional tool: see § Install.

Docs

Status

This package is pre-1.0: the API surface is expected to change, and a minor release may break you. Pin an exact version.

Licence

Apache 2.0. The tarball carries LICENSE and NOTICE.