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

@bugspark/cli

v0.2.5

Published

BugSpark CLI — manage projects and bug reports from the terminal

Readme

@bugspark/cli

Command-line tool for managing BugSpark projects and bug reports.

Install

npm install -g @bugspark/cli

Quick Start

# 1. Login with a Personal Access Token
bugspark login

# 2. Create a project (or pick an existing one)
bugspark init

# 3. List bug reports
bugspark reports list

Authentication

The CLI uses Personal Access Tokens (PATs) for authentication.

  1. Open your BugSpark dashboard → Settings → Personal Access Tokens
  2. Create a token with a descriptive name
  3. Run bugspark login and paste the token when prompted

Your token is stored locally at ~/.bugspark/config.json (file permissions 600).

Commands

Auth

| Command | Description | | ----------------- | ------------------------------- | | bugspark login | Authenticate with BugSpark | | bugspark logout | Remove stored credentials | | bugspark whoami | Show current user info |

Projects

| Command | Description | | ---------------------------------------- | -------------------- | | bugspark init | Interactive setup | | bugspark projects list | List all projects | | bugspark projects create <name> | Create a project | | bugspark projects delete <project-id> | Delete a project |

Reports

| Command | Description | | ------------------------------------------------ | ---------------------- | | bugspark reports list | List bug reports | | bugspark reports list --project <id> | Filter by project | | bugspark reports list --status open | Filter by status | | bugspark reports view <report-id> | View report details | | bugspark reports update <id> --status resolved | Update report status |

Config File

The CLI stores config at ~/.bugspark/config.json:

{
  "apiUrl": "https://api.bugspark.hillmanchan.com/api/v1",
  "token": "bsk_pat_..."
}

Self-Hosted

If you're running a self-hosted BugSpark API, specify the URL during login:

bugspark login
# When prompted, enter your custom API URL

License

MIT