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

opentraces-pi

v0.1.2

Published

OpenTraces capture/search integration for the Pi coding agent

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

jayfareijayfarei

Keywords

pi-packageopentracesagent-tracestrace-capturedatasetbucket

Readme

opentraces-pi

Pi package for OpenTraces. Installs a thin Pi extension, an OpenTraces skill, and prompt templates. The extension observes Pi lifecycle/tool/provider/tree events and forwards normalized sidecars to the Python opentraces bridge.

Install

pi install npm:opentraces-pi

Local development:

pi install ./packages/opentraces-pi
opentraces setup pi --project --local

Package install is quick and reversible. It does not silently install Python, start services, authenticate HuggingFace, enable remote sync, or turn on optional security tools. Capture itself is opt-out: under global tracking (the default) the extension auto-enrolls each repo on first capture, into a private + review-required bucket, once the opentraces CLI is present. Opt out with opentraces config tracking-mode manual or a per-project excluded marker; opentraces init --agent pi still enrolls a repo explicitly.

Raw provider bodies are default-off. Structured context/provider metadata can feed Context Tree; raw bodies are only retained when explicitly opted in and stay local/security-gated.

In Pi

Slash commands are TUI actions for humans:

  • /ot-capture-status — show package, CLI, project capture, raw-body, sidecar, and bucket setup status.
  • /ot-setup — guided local-first setup; asks before enabling project capture.
  • /ot-search <query> — search local retained bucket traces.
  • /ot-trace <trace-id> — resolve one trace and show compact tool evidence.
  • /ot-standup — build a bounded recent-work trace packet.
  • /ot-capsule [trace-id] — preview a trace capsule, or show bucket status without an id.
  • /ot-dataset — list local workflow-built datasets.

Model-facing tools expose the same surfaces: ot_capture_status, ot_search, ot_trace, ot_standup, ot_capsule, and ot_dataset. A typical private bucket workflow is /ot-search farewell helper, then /ot-trace <trace-id> for the selected candidate. ot_search accepts a limit and is read-only against the local snapshot; sync remote traces first with opentraces bucket remote pull. ot_trace can include a compact trace map.

The extension is fail-open. Direct slash commands are not recorded as model tool calls; model-invoked ot_* tools are captured as read-only opentraces_retrieval tool calls. Dataset/capsule actions are retrieval-first; mutating operations such as dataset creation or capsule export should require an explicit user request.