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

@xcelera/cli

v3.0.0

Published

CLI for xcelera.dev

Readme

xcelera CLI

A CLI for running Lighthouse performance audits using xcelera.dev

Usage

CLI Usage

# Basic audit
xcelera audit --ref https://example.com --token your-api-token

Authenticated Pages

For pages behind login, you can pass authentication credentials:

# With session cookie
xcelera audit --ref myapp-com-dashboard --cookie "session=abc123"

# With bearer token header
xcelera audit --ref myapp-com-admin \
  --header "Authorization: Bearer eyJhbG..."

# Multiple cookies
xcelera audit --ref myapp-com-dashboard \
  --cookie "session=abc123" --cookie "csrf=xyz"

# With Netscape cookie file (cookies.txt)
xcelera audit --ref myapp-com-dashboard \
  --cookie-file ./cookies.txt

GitHub Action Usage

- name: Lighthouse Performance Audit
  uses: xcelera/cli@v1
  with:
    ref: myapp-com-dashboard
    token: ${{ secrets.XCELERA_TOKEN }}

For authenticated pages in CI:

# With session cookie
- name: Lighthouse Audit (Cookie Auth)
  uses: xcelera/cli@v1
  with:
    ref: myapp-com-dashboard
    token: ${{ secrets.XCELERA_TOKEN }}
    cookie: "session=value"

# With Netscape cookie file (cookies.txt)
- name: Lighthouse Audit (Cookie File Auth)
  uses: xcelera/cli@v1
  with:
    ref: myapp-com-dashboard
    token: ${{ secrets.XCELERA_TOKEN }}
    cookie-file: ./cookies.txt

# With bearer token header
- name: Lighthouse Audit (Bearer Auth)
  uses: xcelera/cli@v1
  with:
    ref: myapp-com-admin
    token: ${{ secrets.XCELERA_TOKEN }}
    header: "Authorization: Bearer eybDfd..."

# With full auth JSON (multiple cookies/headers)
- name: Lighthouse Audit (Full Auth)
  uses: xcelera/cli@v1
  with:
    ref: myapp-com-dashboard
    token: ${{ secrets.XCELERA_TOKEN }}
    auth: '{"cookies":[{"name":"session","value":"session_value"},{"name":"csrf","value":"csrf_value"}]}'

Setup

1. Get Your API Token

  1. Go to Xcelera Settings
  2. Create a new API token
  3. Copy the token value

2. Add Token to GitHub Secrets

  1. Go to your repository settings
  2. Navigate to "Secrets and variables" → "Actions"
  3. Create a new repository secret named XCELERA_TOKEN
  4. Paste your API token as the value

Development

GitHub Actions are pinned to specific commits. e.g. uses: super-linter/super-linter/slim@7bba2eeb89d01dc9bfd93c497477a57e72c83240 # v8.2.0

To update the pinned versions, run the following command:

pinact run -u