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

naxytra

v3.0.1

Published

Umbrella bootstrap package for the naxytra machine-transaction stack.

Readme

naxytra

naxytra is the umbrella home for the live stack:

  • xytara/
    • runtime and machine-commerce infrastructure
  • xoonya/
    • proof, review, governance, bridge, and followthrough infrastructure
  • _umbrella_service/
    • public-arrival site and umbrella intelligence service

This repo is the clean home for:

  • umbrella narrative and website structure
  • shared planning and release-facing docs
  • umbrella intelligence and public catalog surfaces
  • the relationship between xytara and xoonya

Public Distribution Model

The intended public-facing shape is:

  • naxytra.com
    • public arrival surface
    • public docs and category story
    • product paths for runtime and proof
  • naxytra on npm
    • public bootstrap and umbrella first-contact package
  • xytara on npm
    • public runtime and payment package
  • xoonya on npm
    • public proof and review package

The intended private-facing shape is:

  • source repos
  • operator runbooks
  • treasury landing configuration
  • custody details
  • internal strategy and expansion material

That means the public journey should be:

  • website first
  • npm second
  • real runtime/proof usage immediately after

not:

  • source-code exploration first

Launch assets

For the current public-facing copy pack, see:

Public shape

  • naxytra.com
    • the only public website for the current launch phase
    • umbrella arrival surface
    • product paths for xytara and xoonya
  • naxytra on npm
    • umbrella bootstrap package
  • xytara on npm
    • runtime product package
  • xoonya on npm
    • proof product package

Separate public product websites are deferred. The current public face should stay concentrated on naxytra.com, the naxytra bootstrap package, and the two product packages.

What The Stack Covers

At the system level, the stack already aims to cover:

  • discovery
  • quote
  • direct pay
  • credit funding and top-ups
  • execution
  • dispatch
  • delivery
  • usage metering
  • lifecycle inspection
  • proof and review
  • governance and dispute flows
  • reconciliation and treasury visibility
  • adapter and integration onboarding

Core Layer Breadth

The current 3.0.0 finish-line stack is broader than payment and settlement alone. Across the public two-repo system it already carries:

  • execution-framework lanes such as langchain, langgraph, semantic_kernel, autogen, crewai, and llamaindex
  • protocol and transport lanes such as mcp, a2a, a2c, acp, grpc, mqtt, kafka, nats, ros2, and webhook_event_bus
  • machine-payment fronts such as x402, mpp, l402, bolt, credits, hosted checkout, and direct signed-payment posture
  • proof and verification methods such as XNYA, JWT assertion, DID VC, SD-JWT VC, signed-envelope, detached assertion, and partner proof-envelope compatibility
  • operator and observability lanes such as telemetry, provenance, artifact distribution, shared signals, feature control, reconciliation, and treasury destination visibility

The finish-line goal is not to hide this breadth behind narrower claim language. It is to expose the useful parts cleanly enough that outside agents, builders, and partner systems can discover and use them from naxytra.com, xytara, and xoonya without private tribal knowledge.

Repo layout

  • xytara/
  • xoonya/
  • _umbrella_service/
  • docs/
  • _implementation_closure/
  • _intelligence/
  • NAXYTRA_WORKSPACE_MAP.md

Start here

If you want the shortest route into the live stack:

  • naxytra
    • npm install naxytra
    • naxytra start-here
    • naxytra first-run
  • xytara
    • npm install xytara
    • xytara start-here
    • xytara first-run
  • xoonya
    • npm install xoonya
    • xoonya start-here
  • Public command kit
    • https://www.naxytra.com/v1/first-run-kit
    • https://www.naxytra.com/v1/first-run-kit/summary
  • Public support and ecosystem surfaces
    • https://www.naxytra.com/v1/support-lanes/summary
    • https://www.naxytra.com/v1/ecosystem-lanes/summary
  • Final launch contract surfaces
    • https://www.naxytra.com/v1/3-0-release-contract/summary
    • https://www.naxytra.com/v1/3-0-gates/summary

If you want the public umbrella site locally:

cd _umbrella_service
npm install
npm start

Then open:

http://127.0.0.1:3090

Deployment

For the current phase:

  • Vercel is sufficient for the public umbrella site
  • Render and Supabase remain useful supporting accounts, but are not required to launch the umbrella site

See DEPLOYMENT.md.