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

pi-onedev-toolkit

v0.1.0

Published

Lightweight OneDev integration for Pi via the TOD CLI: repo-aware issue, pull request, and build tools

Readme

pi-onedev-toolkit

Lightweight OneDev integration for Pi, built on the official TOD CLI: repo-aware issue, pull request, and build tools plus issue-to-PR and PR-review skills.

The agent never shells out to tod itself and never sees tokens. The extension resolves the OneDev project from the repository's git remotes once per session, and the tools speak OneDev terms (123, PROJ-123, project#123 all resolve server-side).

Requirements

  • OneDev 15.1+
  • The tod CLI installed and configured:
curl -fsSL https://code.onedev.io/onedev/tod/~raw/main/install.sh | bash
tod config set   # server-url + access-token (or set ONEDEV_SERVER_URL / ONEDEV_ACCESS_TOKEN)

Install

pi install npm:pi-onedev-toolkit
# or from source
pi install git:github.com/alpertarhan/pi-onedev-toolkit

Then run /od-health once. When the current directory is a OneDev repository, the status line shows the active project.

Tools

| Tool | Domains | Covers | | --- | --- | --- | | onedev_tools (always active) | — | Activate domains; session context; login name; download issue/PR attachments | | onedev_issue | issue | Query/get/comment issues, change fields/labels/state, log work, issue branches | | onedev_pull | pull | PR metadata/comments/code comments/labels/builds/patch, create/edit, approve, request changes, guarded merge/discard | | onedev_build | build | Build queries, logs, code-problem reports, changes since last success, run jobs (incl. uncommitted local changes), build-spec validation |

Lazy by design: domain tools activate only through onedev_tools, keeping the default tool list light. merge and discard additionally require confirm: true.

Commands

  • /od-context — active server, inferred project, login
  • /od-health — re-check tod configuration and server reachability

Skills

  • onedev-issue-to-pr — gather issue context, branch, implement, present for review, then push and open the PR
  • onedev-pr-review — full-context PR review with line-anchored findings; submits only on explicit request

Development

bun install
bun run check   # typecheck + vitest

License

MIT