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

@eohutson/tickets

v1.0.5

Published

Lightweight ticket tracking for agentic coding sessions

Downloads

47

Readme

Ticket Tracker

Lightweight ticket tracking for agentic coding sessions. Tickets are managed by LLMs through an MCP server and viewed in a browser-based kanban board.

Usage

npx @eohutson/tickets

This starts both the MCP server (stdio) and the web UI at http://localhost:3000.

All tickets are stored in a single global file at ~/.local/share/ticket-tracker/tickets.json.

Project Prefixes

Create a .tickets file in your project root containing a prefix (e.g., AIP). Tickets will be created as AIP-001, AIP-002, etc. Without a .tickets file, the default prefix is T.

Listing and workable queries only return tickets matching the current project's prefix, so multiple projects share one store without conflicts.

Development

npm install
npm start        # run MCP server + web UI via tsx
npm run ui       # run only the web UI
npm run build    # compile TypeScript to dist/

Ticket Schema

| Field | Type | Description | |--------------------|----------------------------------------------|---------------------------------------| | id | string | Auto-generated (e.g., AIP-001, T-001) | | title | string | Ticket title | | description | string | Ticket description | | status | QUEUED | IN_PROGRESS | DONE | REJECTED | Current status | | priority | 1–5 | 1 = highest, 5 = lowest | | acceptanceCriteria | { description: string, verified: boolean }[] | Testable criteria for completion | | dependsOn | string[] | IDs of tickets that must finish first |

MCP Tools

| Tool | Description | |-----------------|----------------------------------------------------------------------------------| | create_ticket | Create a ticket with title, description, priority, acceptance criteria, deps | | update_ticket | Partial update any field by ticket ID | | get_ticket | Get a single ticket by ID | | list_tickets | List all tickets, optionally filter by status | | delete_ticket | Delete a ticket (fails if other tickets depend on it) | | get_workable | Get QUEUED tickets with all dependencies resolved, optionally sorted by priority |

MCP Configuration

Add to your .mcp.json to use as an MCP server:

{
  "mcpServers": {
    "ticket-tracker": {
      "command": "npx",
      "args": [
        "@eohutson/tickets"
      ]
    }
  }
}

Skills

The manage-tickets skill is automatically installed to ~/.claude/skills/ when the MCP server starts. It activates when you say things like "create a ticket", "what can I work on", or "mark T-001 as done".

Web UI

The kanban board at http://localhost:3000 is read-only and auto-refreshes every 5 seconds. It shows:

  • Four columns: QUEUED, IN_PROGRESS, DONE, REJECTED
  • Priority badges (color-coded P1–P5)
  • Acceptance criteria with verified/unverified indicators
  • Dependency status (blocked vs. ready)