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-maven

v0.2.1

Published

Maven extension for pi — structured test execution, project info, and version lookup

Readme

pi-maven

Maven extension for pi, plus a standalone CLI (tdder-maven) for agents that only have shell access (Claude Code, OpenCode, Cursor, …).

Features

  • maven_run — runs test or package, parses Surefire/Failsafe XML reports, returns structured JSON with failure details (kind, type, file offset)
  • maven_project_info — detects project root, module tree, runner (mvn/mvnw), and available root-pom profiles
  • maven_lookup_version — looks up the latest stable (or pre-release) version of any Maven dependency or plugin from Maven Central
  • maven_available_java_versions — returns available Java releases from Adoptium (latest feature release, latest LTS, release age)
  • /maven command — slash command with live progress widget for info, test, package, version, and java-versions
  • tdder-maven CLI — same functionality as a standalone command for agents that only have shell access

Installation (pi)

pi install git:github.com/t1/tdder

Or install just this package from npm:

pi install pi-maven

CLI (tdder-maven)

Requires tsx on your PATH.

tdder-maven info
tdder-maven test --scope surefire
tdder-maven test --scope all --profiles at
tdder-maven test --scope surefire --selector 'MyTest#myMethod'
tdder-maven test --scope surefire --update-snapshots
tdder-maven test --scope surefire --limit=none
tdder-maven package
tdder-maven package --project module-a --profiles native
tdder-maven lookup-version org.assertj assertj-core
tdder-maven lookup-version io.quarkus quarkus-bom --include-prereleases
tdder-maven available-java-versions
tdder-maven help

All commands output structured JSON to stdout. Non-zero exit code on failure.

Test scopes

| Scope | Behaviour | |------------|--------------------------------------------------------------------| | surefire | Unit tests only (mvn test) | | failsafe | Integration tests only (mvn verify -Dskip.surefire.tests=true …) | | all | Unit + integration tests (mvn verify -DskipITs=false) |

If --scope failsafe returns SUREFIRE_SKIP_NOT_CONFIGURED, follow the instructions in the error response.

Release

  1. npm run sync-extensions (from repo root) — vendor shared code
  2. Bump version in package.json
  3. npm test — verify all tests pass
  4. npm login
  5. npm publish (from this directory)
  6. npm logout