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

buildwithnexus

v0.8.11

Published

Interactive AI agent orchestrator with intent-based planning, execution, and brainstorming modes

Readme

buildwithnexus

npm version License: MIT

Interactive CLI for NEXUS — a 56-agent autonomous software engineering organization. Tell it what to build. It figures out the rest.

Quick Start

npm install -g buildwithnexus
buildwithnexus

On first run you'll be prompted to set your Anthropic API key. Keys are stored in ~/.buildwithnexus/.env.keys.

What It Does

Launch an interactive shell with three execution modes:

  • PLAN — Break down your request into a reviewable step-by-step plan
  • BUILD — Execute directly with live agent streaming
  • BRAINSTORM — Free-form exploration with the NEXUS CPO streaming their reasoning
╔════════════════════════════════════════════════════════════╗
║        Nexus - Autonomous Agent Orchestration              ║
║        v0.8.10                                              ║
╚════════════════════════════════════════════════════════════╝

📝 Task: Build a REST API for user authentication

Press Enter to use PLAN or choose a mode:
  [1] PLAN   design & break down steps
  [2] BUILD  execute with live streaming
  [3] BRAINSTORM  free-form explore & Q&A

Commands

Core (Python backend required)

| Command | Description | |---------|-------------| | buildwithnexus | Launch interactive shell (PLAN/BUILD/BRAINSTORM) | | buildwithnexus da-init | Set up API keys in ~/.buildwithnexus/.env.keys | | buildwithnexus run <task> | Run a task directly via the backend | | buildwithnexus brainstorm [idea] | Brainstorm an idea with the NEXUS CPO | | buildwithnexus server | Start the NEXUS Python backend server | | buildwithnexus da-status | Check backend connectivity | | buildwithnexus doctor | Run diagnostics (backend health + environment) | | buildwithnexus logs [-f] | View server logs (stream with -f) | | buildwithnexus keys list | List configured API keys | | buildwithnexus keys set <KEY_NAME> | Set an API key |

Docker infrastructure (requires Docker + full NEXUS setup)

| Command | Description | |---------|-------------| | buildwithnexus 99 [instruction] | AI pair-programming via full NEXUS engine | | buildwithnexus start | Start full NEXUS Docker services | | buildwithnexus stop | Stop NEXUS Docker services | | buildwithnexus status [--json] | Show Docker container health | | buildwithnexus dashboard | Open the NEXUS dashboard at localhost:4200/dashboard | | buildwithnexus update | Update to the latest version | | buildwithnexus destroy [--force] | Remove NEXUS and all data | | buildwithnexus ssh | Open SSH session into the sandbox |

Architecture

buildwithnexus CLI (TypeScript/Node.js)
         │
         │ SSE streaming
         ▼
NEXUS Backend (Python FastAPI, port 4200)
         │
         ▼
LangGraph Runtime → 56-agent organization
  • CPO (Opus) — brainstorm + strategy
  • VP Engineering → 19 eng agents
  • Product Management → 2 agents
  • QA Team → 7 agents
  • Security Team → 3 agents
  • ML & Data → 6 agents
  • Salesforce → 10 agents
  • Documentation → 2 agents
  • Consultant → 1 agent

Requirements

  • Node.js >= 18
  • Anthropic API key (sk-ant-...) from console.anthropic.com
  • NEXUS backend running on localhost:4200 (for PLAN/BUILD/BRAINSTORM modes)

Optional:

  • OpenAI API key (o3 reasoning support)
  • Google API key (Gemini multimodal support)

Environment Variables

| Variable | Default | Description | |----------|---------|-------------| | ANTHROPIC_API_KEY | — | Overrides stored key | | OPENAI_API_KEY | — | Overrides stored key | | GOOGLE_API_KEY | — | Overrides stored key | | BACKEND_URL | http://localhost:4200 | NEXUS backend address | | NEXUS_BACKEND_DIR | ~/Projects/nexus | Path to NEXUS backend for auto-start |

Security

  • API keys stored in ~/.buildwithnexus/.env.keys with 0600 permissions
  • HMAC-SHA256 tamper detection on .env.keys
  • Input sanitization and output redaction via DLP layer
  • Backend URL validation before transmitting API keys
  • Audit trail at ~/.buildwithnexus/audit.log

Links

License

MIT