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

@codespring-app/v3

v0.1.1

Published

Agent-first CLI for renketsu — context-graph search, ingest, and queries from the terminal.

Readme

v3 — agent CLI for renketsu

Terminal client for renketsu, a context-graph engine for AI agents.

Install

npm install -g @codespring-app/v3

Requires Node.js 22+.

Quick start

# 1. Log in via the OAuth device flow (opens a browser tab)
v3 auth login

# 2. List your projects
v3 project list

# 3. Pick one as the default for subsequent commands
v3 project use proj_xxxxxxxx

# 4. Search the project's context graph
v3 search "what was decided about the auth flow"

# 5. Ask a question (GraphRAG global/local)
v3 ask "what did Alice work on last week" --mode auto

# 6. Stream a long-running ingest
v3 ingest --file ./notes.md --format extract

Auth

v3 auth login runs the standard RFC 8628 device-authorization flow:

  1. The CLI requests a device code.
  2. It opens https://renketsu.codespring.app/device and prefills the user code.
  3. You approve in the browser.
  4. The CLI polls until the API hands back a session token, which is stored at ~/.config/v3/credentials.json (mode 0600).

Override the API URL for self-hosted instances:

v3 auth login --api-url https://your-instance.example.com
# or via env
V3_API_URL=https://your-instance.example.com v3 ...

Commands

v3 auth login | logout | whoami

v3 project list | get <id> | use <id> | create --name NAME

v3 search "<query>" [--top-k N] [--project ID]
v3 stats [--project ID]
v3 graph [--limit N] [--project ID]

v3 ingest --file PATH --format extract|structured|raw [--project ID]
v3 ask "<question>" [--mode auto|global|local] [--project ID]

v3 job list | get <id> | cancel <id> | tail <id>

Run v3 --help for the full command surface.

License

MIT.