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

undernet-coder

v1.0.9

Published

UnderNet Coder for the terminal: an AI coding agent (like Claude Code) powered by UnderNet GPT. Reads, edits and tests your project from any shell.

Readme

UnderNet Coder CLI

The terminal version of UnderNet Coder: an AI coding agent that works like Claude Code, powered by UnderNet GPT (https://safechat.undernet.click, OpenAI-compatible endpoint). Same brain and same tools as the VS Code extension, but it runs anywhere you have a shell: local terminal, SSH, CI, Docker.

◆ UnderNet Coder v1.0.0
folder: /home/me/my-app
mode:   CODE

❯ add a /health endpoint to the express server and a test for it
● Detecting project setup
● Reading src/server.ts · 84 lines
src/server.ts +6 −0
  …
+ app.get("/health", (_req, res) => res.json({ ok: true }));
? Apply this edit? [y]es / [n]o / [a]ll for this task y
  ✓ updated src/server.ts
$ pnpm test
  ↳ exit 0
✓ Added GET /health returning {ok:true} and a vitest case. Verify with `pnpm test`.
  6 steps · 14k tokens · ≈ $0.05 · 2 files changed

Install

Requires Node.js 18.17+ (Node 20+ recommended).

npm install -g undernet-coder

That gives you the aye command (and undernet-coder). Mirror without npm registry access: npm install -g https://undernet.work/downloads/undernet-coder-cli.tgz.

Updates are automatic: once a day it checks npm and, if there is a newer version, installs it quietly in the background so the next start uses it. aye update installs immediately; /set autoUpdate false turns the background install off (you still get a notice).

From source

pnpm install
pnpm build
npm link            # `aye` now points at this folder

Publishing a new version

npm version patch   # bumps package.json, commits and tags
npm publish         # runs check-types, tests and bundle first (prepublishOnly)
pnpm release        # optional: refresh the tarball mirror in the web app's downloads folder

First run

cd your-project
undernet

Paste your UnderNet API key (starts with sc-, from https://undernet.work) when asked. It is stored in ~/.undernet-coder/config.json. You can also set UNDERNET_API_KEY in the environment, which takes precedence.

Usage

undernet                          interactive session in the current folder
undernet "fix the failing tests"  run one task, stay interactive
undernet -p "summarise src/"      print mode: no prompts, auto-approve, exit code 0/1 (scripts, CI)
undernet --ask                    confirm each edit and command (auto-approve is the default)
undernet --plan                   start read-only, get a numbered plan, say "go" to execute
undernet -c                       continue the last task in this folder
undernet -r <id>                  resume a task from /history
undernet -C ../other-project      work in another folder

Inside a session:

| Command | What it does | | --- | --- | | /plan, /code | Switch between read-only PLAN mode and CODE mode | | /auto on\|off | Auto-approve edits and commands. On by default (same as the extension); /auto off or aye --ask makes it confirm each step | | /key | Set or replace the API key | | /wallet | Show balance | | /changes, /undo, /revert <file> | See and undo what this task changed (git checkpoint when the folder is a repo) | | /history, /resume <n>, /delete <n> | Recent tasks (kept in ~/.undernet-coder/history) | | /new | Start a fresh task | | /settings, /set <key> <value> | Same settings as the extension: autoApproveEdits, autoApproveCommands, maxSteps, instructions, maxOutputTokens, reasoning (low/high), webSearch, temperature, maxCostPerTask (0 = no limit, the default), gitCheckpoints | | /cost | Tokens and estimated cost | | /exit | Quit (Ctrl+C twice also works) |

Extras: @path/to/file attaches a file to your message, !cmd runs a shell command directly, and ending a line with \ continues on the next line. Ctrl+C during a task stops it.

Persian/Arabic text: Windows consoles and VS Code's terminal do not join Arabic letters or apply right-to-left order, so the CLI shapes and reorders such text itself (model output and what you type). It is on automatically on Windows and in VS Code; /set rtl on|off|shape overrides: off for a terminal that renders RTL natively (some Linux terminals), shape for one that orders right-to-left itself but does not join letters.

AGENTS.md and .undernet-coder.md in the project root are sent with every task (the agent writes notes to the latter with its remember tool).

Tools the agent has

Files: list_files, read_file, read_lines, search, grep (ripgrep when available), write_file, apply_patch, multi_edit, delete_file, move_file, create_directory, format_file, revert_file. Code intelligence: get_diagnostics (runs tsc and eslint, returns path:line:col), outline, go_to_definition, find_references, rename_symbol (TypeScript/JavaScript, via the project's own typescript package). Commands: run_command, run_in_background, run_tests, list_processes, read_process_output, stop_process, kill_port, wait, env_info, detect_project. Network: fetch_url, http_request, open_in_browser, plus a headless browser (browser_open, browser_screenshot, browser_click, browser_type, browser_console, browser_close) when playwright-core and Chrome/Edge are installed. Git: git_status, git_diff, git_log, git_branch, git_stash, git_commit. Control: ask_user, remember, switch_mode, task_complete.

Differences from the VS Code extension: there is no editor, so get_editor_context, install_extension and open_file do not exist. Read-only tool calls issued together in one reply run in parallel, and a dropped connection mid-reply is resumed automatically (up to 3 times) without losing the text already streamed.

Build and test

pnpm check-types   # tsc
pnpm test          # unit tests + agent-loop integration tests against a scripted mock server (parallel tools, PLAN mode, reconnect)
pnpm bundle        # esbuild → dist/cli.js (single file, no runtime deps)