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

@auroraflow/code

v0.0.12

Published

Aurora launcher and sidecar for official Codex and Claude Code clients.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

auroraflowauroraflow

Keywords

Readme

Aurora Code

Unified Aurora launcher for official Claude Code and Codex clients.

Layout

packages/cli       command entrypoints and init flow
packages/clients   official Claude/Codex launch adapters
packages/sidecar   local HTTP proxy for runtime traffic
packages/protocol  shared rewrite/projection helpers
packages/state     ~/.aurora state paths and JSON state
bin/               npm bin shims
lib/               current MVP support modules

Install

Installing @auroraflow/code as a global npm package attempts to install/update the official Claude Code and Codex global commands:

npm install -g @auroraflow/code

Aurora does not export claude or codex bins. The standalone claude and codex commands remain the official clients and keep their official behavior. Aurora only wraps them through aurora-claude and aurora-codex.

To install or update the official clients explicitly:

aurora install-clients
aurora update-clients

Commands

npm run check
scripts/release_npm.sh 0.0.7
node bin/aurora.js
node bin/aurora.js init
node bin/aurora.js claude
node bin/aurora.js codex
node bin/aurora.js install-clients
node bin/aurora.js update-clients
node bin/aurora.js status

Running aurora without a subcommand opens an interactive client selector. Use Up/Down (or j/k) and Enter to launch Claude or Codex through Aurora.

The launcher stores shared local state under ~/.aurora and starts a local sidecar at 127.0.0.1:17878. Official clients talk to the sidecar; the sidecar injects the selected Aurora key/model and forwards runtime traffic to Aurora Gateway.

The Aurora desktop client is the product path for model/key selection. Its local runtime workbench writes ~/.aurora/agent-state.json; aurora-claude and aurora-codex only consume that local runtime state and route official client traffic through the sidecar. The clients are launched with the selected Aurora model alias, and the sidecar enforces the same selected alias when forwarding runtime requests. aurora-codex also writes ~/.aurora/clients/codex/config.toml and auth.json before launch so Codex uses the Aurora sidecar provider instead of the OpenAI login flow.