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

@voxli/cli

v0.5.0

Published

CLI agent for running Voxli test scenarios locally

Readme

@voxli/cli

CLI agent for running Voxli test scenarios locally.

Install

npm install -g @voxli/cli

Requires Node.js 18+.

Setup

Authenticate with your Voxli account:

voxli auth

This opens your browser to app.voxli.io where you log in and approve access. An API key is created automatically and saved to ~/.voxli/config.json.

To enter an API key manually instead:

voxli auth --manual

You can also set the VOXLI_API_TOKEN environment variable instead.

Usage

Start listening for test work:

voxli listen --command "<your test command>"

The CLI polls the Voxli API for pending test batches. When work arrives, it spawns your command as a subprocess with these environment variables:

| Variable | Description | |---|---| | VOXLI_API_TOKEN | Your API key | | TEST_RESULT_IDS | JSON array of test result IDs to run | | RUN_ID | The run ID (if part of a run) |

Commands

| Command | Description | |---|---| | voxli auth | Authenticate via browser | | voxli auth --manual | Authenticate by entering an API key manually | | voxli listen --command <cmd> | Poll for pending test work and run it locally |