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

@allocator-one/infraone

v1.30.1

Published

Infra One from the terminal: your data rooms, with exactly your app rights

Vulnerabilities

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

Links

Git

Maintainers

mstroeckmstroeck

Keywords

Readme

@allocator-one/infraone

The infraone CLI: what you can do in Infra One, from a terminal or a script, with exactly your app rights. It starts with your data rooms.

Install

With npm (Node 20 or later):

npm i -g @allocator-one/infraone
infraone --help

Or run it without installing:

npx -y @allocator-one/infraone --help

With Homebrew, on macOS or Linux:

brew install allocator-one/tap/infraone

As a single binary for macOS or Linux, with no Node needed. The script downloads the binary for your machine, checks its SHA-256 checksum, and installs it in ~/.local/bin (set INFRAONE_INSTALL_DIR to choose another folder):

curl -fsSL https://github.com/allocator-one/homebrew-tap/releases/latest/download/install.sh | sh

Sign in

infraone login
infraone whoami

infraone login opens Infra One in your browser. You choose the organization there, and the CLI stores a credential for it that lasts 30 days. Every command then acts as you, in that organization, with the rights you have in the app. Signing in covers other organizations, scripts and signing out, and personal tokens are the credential to give a script.

Use it

infraone datarooms spaces list
infraone datarooms spaces list --type personal --json

The commands come from the Infra One API, so infraone --help always lists what the server offers, including commands added after this release. Every command takes --json. Lists page with --limit and --cursor, and --all follows every page. The command reference lists the commands this release knows about, and the app pages show each app's commands and MCP tools, the scopes they need, the ones that ask you to confirm, and what stays in the app. Both are generated at release from the API's spec and ship in the npm package.

Deleting, revoking access, sharing outside Infra One and emailing people ask you to confirm first; confirmations explains how.

AI clients

Connect Claude, or any MCP client, to the hosted Infra One MCP at https://mcp.infra.one/mcp. Infra One MCP shows how.

Exit codes

| Code | Meaning | |---|---| | 0 | Done | | 1 | The API refused or failed the request | | 2 | The command line was wrong, or a confirmation was missing; nothing was sent | | 3 | The API could not be reached |

stdout carries data only; messages go to stderr.