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

@facetlayer/tickets-tool

v0.2.0

Published

CLI tool for locally storing and searching tickets and bug reports

Readme

tickets-tool

CLI tool for storing and searching tickets and bug reports. Similar to a lightweight issue tracking system.

Installation

pnpm build && npm i -g .

Usage

Report feedback

Create a new ticket:

tickets report -l <library> -d <description> [options]

Options:

  • -l, --library (required): Target library name
  • -d, --description (required): Feedback description
  • -s, --severity: Severity level (critical, high, medium, low, positive). Default: medium
  • -c, --context: Additional context (e.g., stack trace, environment)
  • -u, --user: User who reported the feedback

Examples:

# Report a bug
tickets report -l my-library -d "Function throws error on empty input" -s high

# Report with context
tickets report -l api-client -d "Timeout on large requests" -s critical -c "Happens with payloads > 1MB" -u alice

# Report positive feedback
tickets report -l utils -d "Great error messages, very helpful!" -s positive -u bob

List feedback

Search and list tickets:

tickets list [options]

Options:

  • -l, --library: Filter by library name
  • -s, --severity: Filter by severity level
  • -u, --user: Filter by user
  • -n, --limit: Number of items per page (default: 20)
  • -p, --page: Page number, 1-based (default: 1)

Examples:

# List all tickets
tickets list

# List tickets for a specific library
tickets list -l my-library

# List only critical issues
tickets list -s critical

# Paginate through results
tickets list -n 10 -p 2

Data Storage

Tickets are stored in a SQLite database at ~/.local/state/tickets-tool/db.sqlite (following XDG standards).

Development

pnpm build   # Build the project
pnpm test    # Run tests