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

@louedev/wemiy

v1.2.6

Published

Better Auth powered device-flow authentication CLI with AI workspace

Readme

Wemiy CLI

AI-assisted CLI for fixes, project health checks, commits, reviews, and PR prep. Published as @louedev/wemiy (binary: wemiy).

Banner

Features

  • Fix — AI-assisted fixes for a file
  • Doctor — Scan the project for bugs, performance, security, and bad practices (--changed-only, --max-files, optional cache)
  • Commit — Conventional commit messages from your diff
  • Review — AI code review for current changes
  • PR Ready — Review/fix changed files, tests, commit message, PR description
  • Agent — Agentic workflows (optional --conversation to continue a saved thread)
  • Conversations — List, show, export, fork, and resume saved transcripts (~/.orbital-cli/chats.json)
  • Model — Switch provider (Gemini, OpenRouter, SwiftRouter)
  • Wake Up — Daily assistant prompt
  • Login / Logout / Whoami — Better Auth device flow (optional; requires the auth server)

Repository layout

| Path | Role | |------|------| | server/ | CLI package (wemiy), Express API + Prisma + Better Auth | | client/ | Next.js app for auth/device flow | | react-tailwind-todo-app/ | Sample app (not required for the CLI) | | ecommerce-site/ | Static demo site (optional) |

Installation

From npm:

npm install -g @louedev/wemiy

From this repo:

git clone https://github.com/yuncko/wemiy-cli.git
cd wemiy-cli/server
npm install
npm link

Environment variables

| Variable | Purpose | |----------|---------| | OPENROUTER_API_KEY | OpenRouter provider | | GEMINI_API_KEY / Google env | Gemini (see provider docs) | | BACKEND_URL | Auth server URL for wemiy login (default http://localhost:3005) | | FRONTEND_URL | Web app origin for CORS/device flow | | ORBITAL_DEBUG or WEMIY_DEBUG | Set to true for debug logs |

Secrets: Prefer environment variables for API keys. If you store keys in ~/.wemiy/config.json, treat that file like a credential — restrict permissions and never commit it.

Create server/.env for local API development (see server README patterns).

Commands

wemiy doctor [--path <dir>] [--fix] [--json] [--changed-only] [--max-files <n>] [--use-cache]
wemiy fix <file>
wemiy commit
wemiy review
wemiy pr-ready [--dry-run]
wemiy model
wemiy agent [--conversation <uuid>] [--mode act|discuss] [--auto-approve] [--max-iterations <n>] [-y]
wemiy conversations list
wemiy conversations show <uuid> [--json|--markdown] [--full]
wemiy conversations export <uuid> [-o <file>]
wemiy conversations fork <uuid> [--until-message <message-uuid>]
wemiy conversations resume [--max-iterations <n>] [-y]
wemiy wake-up
wemiy login [--server-url <url>]

Examples:

wemiy doctor --path .
wemiy doctor --changed-only --max-files 20
wemiy pr-ready --dry-run
wemiy fix src/app.js

Context, memory, and conversation replay

Chats and agent runs are stored locally in ~/.orbital-cli/chats.json.

Typical flow

  1. List conversations: wemiy conversations list and copy a conversation ID.
  2. Inspect a thread: wemiy conversations show <id> or wemiy conversations show <id> --json.
  3. Continue: wemiy agent "your follow-up" --conversation <id> (add --mode discuss for read-only Q&A).
  4. Or run: wemiy conversations resume for an interactive picker.

Export and fork

  • wemiy conversations export <id> -o backup.json saves the conversation and all messages.
  • wemiy conversations fork <id> copies the thread to a new ID. Use --until-message <msgId> to copy only messages up to that point. Continue with --conversation on the new ID.

Project memory (optional)

Add .wemiy/memory.md in the repo (Markdown). The agent loads a capped excerpt into the system prompt. Do not put secrets there.

Tech stack

  • Node.js (ESM), Commander, AI SDK / providers
  • Express 5 + Better Auth + Prisma (auth API in server/)

Contributing

Issues and PRs are welcome. Run tests from server/:

cd server && npm test

License

MIT