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

@sbuglione/open-cli

v0.0.4

Published

Remote-first API and MCP command client for open-cli

Readme

@sbuglione/open-cli

Remote-only API and MCP command tooling with a separately installed hosted runtime.

What is open-cli?

open-cli converts OpenAPI specs and MCP server definitions into executable CLI commands, so you can explore, test, and audit APIs from your terminal. open-cli always connects to a separately hosted runtime server (open-cli-toolbox), which handles catalog execution, token-scoped tool exposure, policy evaluation, and enterprise deployment concerns.

Platform Support

| OS | x64 | arm64 | |---------|-----|-------| | macOS | ✓ | ✓ | | Linux | ✓ | ✓ | | Windows | ✓ | ✓ |

Installation

npm install -g @sbuglione/open-cli

What happens during install

The postinstall script automatically downloads the correct pre-built open-cli binary for your platform from GitHub Releases. No compiler or Go toolchain is needed.

open-cli-toolbox is not bundled in the npm package. Install it separately from the same GitHub Releases page or build/run it via the repo's Docker flow if you need the reference hosted runtime.

Quick Start

# 1. Install the client
npm install -g @sbuglione/open-cli

# 2. Point open-cli at your hosted runtime
open-cli --runtime https://toolbox.example.com

# 3. Initialize your own API catalog
open-cli init <your-api>

open-cli does not embed a local execution daemon. Operators host open-cli-toolbox, secure it, and decide which tools are visible to each token.

Troubleshooting

| Problem | Cause | Solution | |---------|-------|----------| | binary not found at … | postinstall didn't run or failed | Run npm install -g @sbuglione/open-cli again | | HTTP 404 during install | Version/platform mismatch or unpublished release | Check releases for your platform | | SSL / proxy errors | Corporate proxy or firewall blocking GitHub | Set https_proxy env var or download the binary manually | | Download timeout | Slow connection | Set OPEN_CLI_DOWNLOAD_TIMEOUT=120 (seconds) before install | | permission denied | Binary lacks execute permission | Run chmod +x $(npm prefix -g)/lib/node_modules/@sbuglione/open-cli/bin/open-cli |

Configuration

See the full documentation at https://open-cli.dev/ for configuration options, policy files, and advanced usage.

License

GPL-3.0