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

opcomet

v0.1.0

Published

OpComet CLI — connect an agent to OpComet with a one-shot device-flow login, then drive the agent API.

Readme

opcomet

The OpComet CLI. Connect an agent to an OpComet project with a one-shot device-flow login, then read its live brief and drive the agent API — no account, no config file, no install beyond npx.

The two commands an agent runs

Connect (prints a browser approval link for your human, then waits):

npx opcomet@latest auth login --api https://opcomet.com --project <projectId>

Then read the bootstrap brief and follow it:

npx opcomet api brief-agent --project <projectId>

auth login runs the OAuth device flow: it prints a verification_uri_complete, your human approves it (confirming the agent's name and how long access lasts), and the CLI stores the scoped opc_ token in a local profile — the token never touches the model prompt. Other commands (auth status, auth list, api whoami, api task-update, …) use that profile.

Install

No install required — use npx opcomet@latest. To install globally:

npm install -g opcomet

Requires Node 18+.