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

@elytro/wrapper

v0.2.1

Published

Natural-language frontend for the Elytro CLI — translates plain-English input into elytro commands using a local LLM and returns structured JSON results.

Downloads

165

Readme

elytro-wrapper

A natural-language frontend for the Elytro Ethereum smart-account CLI. You describe what you want in plain English; elytro-wrapper translates it into the correct elytro command, executes it, and returns the result as structured JSON.

The model runs entirely on your machine — no remote API calls are made.

How it works

User input (natural language)
        │
        ▼  node-llama-cpp + Qwen3-0.6B (local)
elytro CLI command(s)
        │
        ▼  child_process.spawn
JSON result

Requirements

npm install -g @elytro/cli

Installation

npm install -g @elytro/wrapper

The postinstall script downloads the Qwen3-0.6B-Q8_0.gguf model (~640 MB) automatically. If the download is interrupted you can re-run it at any time:

npm run download-model

Usage

elytro-wrapper "<natural language input>"

Examples

elytro-wrapper "check my balance"
elytro-wrapper "show all accounts"
elytro-wrapper "what chain am I on"
elytro-wrapper "switch to agent-primary"
elytro-wrapper "send 0.01 ETH to 0xRecipient"

Output format

Every invocation prints a JSON array to stdout. Each element corresponds to one executed command:

[
  {
    "cmd": "elytro query balance",
    "succ": true,
    "stdout": "{ \"success\": true, \"result\": { ... } }",
    "stderr": ""
  }
]

| Field | Type | Description | | -------- | --------- | ---------------------------------------- | | cmd | string | The full command string that was run | | succ | boolean | true when the exit code was 0 | | stdout | string | Raw standard output from the command | | stderr | string | Raw standard error output from the command |

Error cases

| Situation | cmd | succ | |---|---|---| | Input cannot be mapped to a command | __UNKNOWN__ | false | | Command not in allowlist | original string | false | | Command execution fails | original string | false |

Multi-step commands

Some operations require multiple commands to be run in sequence. elytro-wrapper handles this automatically:

# swap: quote is always fetched before sending
elytro-wrapper "swap 1 ETH for USDC"
# → elytro swap quote ...
# → elytro swap send ...

# tx send: simulation always runs before broadcast
elytro-wrapper "send 0.01 ETH to 0xRecipient"
# → elytro tx simulate ...
# → elytro tx send ...

Development

# install dependencies
npm install   # also downloads the model via postinstall

# run without building
npm run dev "check my balance"

# build
npm run build

# run built output
node dist/index.js "check my balance"

Project structure

├── src/
│   ├── index.ts       # CLI entry point
│   ├── llm.ts         # LLM inference (node-llama-cpp + Qwen3-0.6B)
│   ├── prompt.ts      # System prompt
│   ├── executor.ts    # Command execution
│   └── whitelist.ts   # Command allowlist guard
├── scripts/
│   ├── download-model.mjs   # Model download script (postinstall)
│   └── load-env.mjs         # Dev .env loader
├── models/            # Downloaded model files (gitignored)
└── tsup.config.ts

Security

All commands generated by the LLM are validated before execution. Commands that do not start with elytro are rejected with an error result and never spawned.

Write operations (fund transfers, security configuration changes, etc.) are generated by the LLM and included in the output like any other command. The calling process or agent is responsible for prompting the user for confirmation before acting on write operations.