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

nexarch

v0.12.3

Published

Your architecture workspace for AI delivery.

Readme

nexarch

Your architecture workspace for AI delivery.

Quick start

npx nexarch login
npx nexarch setup

setup, mcp-config, and init-agent are registry-driven and fail closed. If the published integration registry is unavailable/invalid, these commands stop until service is restored.

Commands

| Command | Description | |---|---| | nexarch login [--company <id>] | Authenticate via browser and store company-scoped credentials; prompts for company when multiple memberships exist | | nexarch logout | Remove local credentials | | nexarch status | Check connection, registry health/version, and architecture summary for the company selected at login | | nexarch setup | Auto-configure detected MCP clients | | nexarch mcp-config [client] | Print config block for manual setup (supported client codes are registry-managed) | | nexarch mcp-proxy | stdio→HTTP bridge used internally by MCP clients | | nexarch init-agent [--json] [--strict] [--agent-id <id>] [--redact-hostname] | Run onboarding handshake and mandatory agent entity registration in graph | | nexarch init-agent --bind-to-external-key <key> [--bind-relationship-type <code>] | Optionally bind the agent node to an existing graph external key | | nexarch init-agent (default behavior) | Also upserts technology component entities (host, OS, Node.js runtime) and links them to the agent | | nexarch agent identify ... | Submit provider/model/client identity metadata to complete agent profile enrichment |

Bootstrap flow after init-agent

nexarch init-agent writes a bootstrap file at:

~/.nexarch/agent-bootstrap.md

That file contains a pre-filled npx nexarch agent identify ... command template. The current workflow is:

  1. run npx nexarch init-agent
  2. open ~/.nexarch/agent-bootstrap.md
  3. copy the generated npx nexarch agent identify ... template
  4. fill in the real provider/model/client details
  5. run the completed command

Do not assume an npx nexarch agent prompt command exists unless/until it is explicitly implemented and documented.

Company context behavior

  • Company is selected during nexarch login.
  • If your user has one active company, login auto-selects it.
  • If your user has multiple active companies, login requires explicit selection.
  • To switch company later, run nexarch login again and pick another company.

Requirements

  • Node.js 18 or later
  • A Nexarch workspace account

Documentation

nexarch.ai/docs/cli-reference