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

opencode-trace-logger

v0.1.6

Published

OpenCode plugin for collecting coding-agent traces

Readme

opencode-trace-logger

OpenCode plugin that records agent events and tool calls to local JSONL trace files.

Traces are written under:

~/ai-traces/<project>/<session>/

Each session directory includes:

  • events.jsonl for plugin, event, and tool execution records
  • final.diff captured when opencode exits
  • git-status-final.txt captured when opencode exits

The logger redacts common API keys, GitHub tokens, bearer tokens, passwords, and token fields before writing events.

Install

Install into opencode with:

opencode plugin opencode-trace-logger

Or add it manually to ~/.config/opencode/opencode.json:

{
  "$schema": "https://opencode.ai/config.json",
  "plugin": ["opencode-trace-logger"]
}

Restart opencode after changing config so the plugin is loaded.

This package includes a TUI target for opencode's plugin installer, but trace collection runs through the server plugin entrypoint above.

Local Development

Build the package:

npm run build

Test the local build by adding the compiled file to opencode config:

{
  "$schema": "https://opencode.ai/config.json",
  "plugin": ["file:///absolute/path/to/opencode-trace-logger/dist/index.js"]
}

If testing through the TUI plugin installer, use the package root rather than dist/index.js; the TUI target is exported at opencode-trace-logger/tui.