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

@jonathlima/orquestra

v0.1.1

Published

Orquestra local-first orchestration runtime with automated init, DAG execution, skill routing, and evidence-based verification.

Readme

@jonathlima/orquestra

Orquestra is a local-first orchestration harness for AI coding CLIs. The npm package installs the native runtime and portable Agent Skills; the selected AI host performs the reasoning while the runtime enforces state, confidence, routing, DAG execution, checkpoints, and evidence-based verification.

Install

npm install --global @jonathlima/orquestra

Or run it without a global installation:

npx @jonathlima/orquestra doctor --security
npx @jonathlima/orquestra setup --host opencode

Register Orquestra once in each host you use:

orquestra setup --host codex
orquestra setup --host claude-code
orquestra setup --host opencode
orquestra setup --host antigravity

Use --dry-run to inspect every setup change before it is written.

Start A Request

After the one-time host setup, orquestra-init is the public entry point. Add the complete problem after the command:

Codex:       $orquestra-init <problem>
Claude Code: /orquestra-init <problem>
OpenCode:    /orquestra-init <problem>
Antigravity: invoke the orquestra-init skill with <problem>

The host then drives the complete flow: focused grilling, mapped web research, cross-source validation, confidence convergence, demand-specific planning, inventory-based skill routing, project-local BRAIN adaptation, DAG dispatch, checkpoint approval, rerouting after failed attempts, and strict verification.

The default convergence threshold is 0.95. Projects can adjust it in .orquestra/config.toml under [init] min_confidence within the runtime's allowed range.

Product Checks

orquestra doctor --security
orquestra update check
orquestra skill scan
orquestra brain policy

Project state and audit evidence are stored under .orquestra/. Installed global skills are read-only; adaptations are created only inside the current project and require review before activation.

Supported Platforms

Prebuilt packages are selected automatically by npm for Windows x64, macOS x64/ARM64, and Linux x64/ARM64.

Version history and comparisons are published in GitHub Releases.

License

Copyright (C) 2026 Jonathan Lima.

Orquestra is licensed under the GNU Affero General Public License v3.0 only. Distribution of this package or its native binaries must be accompanied by equivalent access to the Corresponding Source under the AGPLv3 terms. Modified versions used for remote network interaction must offer their Corresponding Source to the users interacting with them.