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

oasis-observer

v0.2.2

Published

Connect Claude Code and Codex to your Oasis workspace. Shared outcomes, automatic task attribution, and team usage.

Readme

Oasis Observer

Your tools. Your team. One place to understand the work.

Connect Claude Code and Codex to your Oasis workspace. Keep using your own AI accounts: Oasis organizes shared outcomes in the background and shows each person's, agent's, and model's contribution in the existing dashboard.

Get started

Install the native plugins directly from the Oasis marketplace, then use the bundled Connect Oasis action. Node.js 24+ is required; a separate npm installation is not. See the native installation and company rollout guide.

The guided npm installer is an alternative. Use it with an Oasis deployment that supports Observer enrollment, connection status, and activity ingestion.

You need Node.js 24 or newer, a supported local Claude Code or Codex installation, and an Oasis account.

From your work folder, run:

npx [email protected] setup
  1. Choose your tools and the work folder to observe.
  2. The installer adds the native Oasis plugins. Sign into Oasis in your browser and choose your workspace.
  3. Return to the installer. Review the hooks in each tool, then start a fresh work session. Codex requires native hook approval through /hooks.
  4. Check your connection:
npx [email protected] status --wait 60

A workspace connection confirms enrollment. A received activity timestamp confirms that this device has delivered activity. Tasks are created or linked by Oasis's task-board agent when the work has an identifiable outcome; a greeting or setup check may correctly have no task.

Connect your workspace · Open Oasis

What works

| Tool | Supported installation | | --- | --- | | Claude Code | Local sessions on macOS and Linux. | | Claude Desktop Code | Local mode with an enrolled work folder; shared Claude Code hooks. Validate the first session on your installed Desktop version. | | Codex | Local CLI and compatible Desktop runtimes with native hooks enabled and trusted. Validate the first session on your installed Desktop version. | | Cowork, ChatGPT, Copilot, cloud/remote sessions | Separate integrations; this local installer does not enable them. |

Cowork's hook capability is not the same as compatibility with this collector. Windows guided setup has not been validated. Provider updates can change native transcript formats; missing fields are reported rather than fabricated.

Personal Claude Code and Codex subscriptions can share an Oasis workspace. Each employee signs into their own Oasis identity. No shared provider enterprise account, manual task selection, or per-session activation is required after setup.

Work folders and company rollout

To connect specific tools and several work folders:

npx [email protected] setup \
  --source claude_code --source codex \
  --work-root /work/product --work-root /work/docs

An administrator can distribute Node and install the reviewed plugins without signing in as an employee:

npx [email protected] setup --yes --install-only \
  --source codex --work-root /work/product

Each employee then runs setup and signs into their own Oasis account. An existing compatible enrollment is reused. Use setup --reauth to choose another account or workspace. Setup will not overwrite a marketplace managed by another source.

For a separate Oasis deployment, supply both --api-url and --web-url. Never share an enrollment credential between people or copy your local configuration to a teammate.

Your data

Capture is limited to enrolled sources and work folders. Oasis receives bounded prompt, response, and tool context plus available native usage and identity metadata. Existing session history is not imported. The client never selects tasks or starts the proactive Task Manager.

Only a scoped device token is saved locally, with user-only file permissions. Events enter a bounded local queue and are retried without changing their identity. Provider usage gaps and costs that were not supplied remain unavailable. Codex counters are not authoritative per-request billing records; subscription invoices are not inferred from token counts.

Useful commands:

npx [email protected] status --json
npx [email protected] flush
npx [email protected] logout

logout revokes this device's credential and stops future collection. Deliver queued work before logging out. flush --retry resumes delivery after you have resolved a permanent authentication or server error. Re-running setup installs the current package's plugins through the native managers; updated hooks may require another review and fresh sessions.

If a revoked connection makes delivery impossible, logout --discard-pending revokes the device first, then permanently discards its queued activity and reports the counts. That undelivered work will not appear in Oasis and cannot be recovered by signing in again. A failed revocation preserves the queue. Run setup afterward to create a fresh connection; pending work is never moved to another identity.

Development

The collector uses Node's standard library and has no runtime dependencies. npm test checks capture, replay, isolation, enrollment and installation behavior. npm run build creates the native plugin marketplace; npm pack includes it in the publishable package. The actual tarball is tested before release. Internal development and provider-contract notes are in docs/development.md.