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-idle-workspace-reaper

v0.1.1

Published

OpenCode plugin that disposes idle workspaces and reacts to session disposal events.

Vulnerabilities

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

Links

Git

Maintainers

isac322isac322

Keywords

opencodeopencode-pluginworkspaceidle

Readme

OpenCode Idle Workspace Reaper

OpenCode plugin that disposes a workspace after one hour of inactivity, using a five-second confirmation pass and a five-minute retry after SDK failures. It also disposes immediately when the current workspace session is archived or deleted, and stops its timers when OpenCode reports that the current directory's server instance was already disposed. It vetoes idle disposal while a session is busy or a PTY is running, scopes status, PTY, log, and dispose calls to the plugin directory, and only disposes through the explicit hook lifecycle.

Install with npm install opencode-idle-workspace-reaper, then point OpenCode at the installed package entry file under node_modules/opencode-idle-workspace-reaper/index.ts. For local development, configure OpenCode with file:///home/bhyoo/projects/typescript/opencode-idle-workspace-reaper/index.ts. Run bun install, then bun run check.

Limitation: a separate plugin cannot observe an OMO task stuck pending before session creation for over one hour.

Releasing

The first npm publish for 0.1.1 is manual so the package exists on npm. Future publishes use npm Trusted Publishing through GitHub Actions OIDC; do not add an npm token or NODE_AUTH_TOKEN secret for publishing.

After 0.1.1 exists on npm, configure the package on npmjs.com under Settings → Trusted Publisher with these values:

  • Publisher: GitHub Actions
  • Organization or user: isac322
  • Repository: opencode-idle-workspace-reaper
  • Workflow filename: publish.yml
  • Environment name: leave blank
  • Allowed action: npm publish

For each later release, bump package.json, commit, tag the same version as vX.Y.Z, push the commit and tag, then publish a GitHub Release for that tag. The .github/workflows/publish.yml workflow checks the package, verifies the release tag matches package.json, and runs npm publish through OIDC. The first CI-published version should be 0.1.2 or newer, because 0.1.1 is reserved for the manual bootstrap publish.

npm provenance is generated automatically for GitHub Actions trusted publishing only when the package and source repository are public. If this GitHub repository stays private, OIDC publishing can still be configured but npm provenance will not be generated.