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

jcli-dc

v1.1.0

Published

Lightweight CLI for Jira Data Center — issue search, sprint management, and more via PAT auth

Downloads

207

Readme

jcli-dc

Lightweight CLI for Jira Data Center — search issues, manage sprints, and interact with your on-prem Jira instance from the terminal. All output is JSON, making it ideal for scripting and LLM-assisted workflows.

Note: This tool targets Jira Data Center (Server) REST API v2 and Agile API v1. It is not intended for Jira Cloud.

Install

npm install -g jcli-dc

Requires Node.js >= 18.

Quick Start

# Configure your Jira connection
jcli config set --url https://jira.example.com --token YOUR_PERSONAL_ACCESS_TOKEN

# Verify connectivity
jcli config test

# Get your assigned issues
jcli issue mine

Authentication

jcli uses Personal Access Tokens (PAT) — the recommended auth method for Jira Data Center 8.14+.

To create a PAT: Jira → Profile → Personal Access Tokens → Create token.

Your config is stored at ~/.jcli/config.json.

Commands

Config

| Command | Description | | ------------------------------------------------------------- | ------------------------------------- | | jcli config set --url <url> --token <pat> [--email <email>] | Save connection details | | jcli config show | Display current config (token masked) | | jcli config test | Test connectivity |

Issues

| Command | Description | | --------------------------------------------------------- | -------------------------- | | jcli issue mine | Issues assigned to you | | jcli issue mine --status "In Progress" | Filter by status | | jcli issue mine --project PROJ | Filter by project key | | jcli issue mine --max 20 | Limit results | | jcli issue get PROJ-123 | Get full issue detail | | jcli issue get PROJ-123 --comments | Include comments | | jcli issue search "project = PROJ AND status = 'To Do'" | Raw JQL query | | jcli issue comment PROJ-123 "Fixed the thing" | Add a comment | | jcli issue transitions PROJ-123 | List available transitions | | jcli issue transition PROJ-123 31 | Transition an issue | | jcli issue assign PROJ-123 jane.doe | Assign to a user |

Sprints & Boards

| Command | Description | | ------------------------------------------- | ------------------------ | | jcli sprint boards | List all boards | | jcli sprint boards --name "My Board" | Search boards by name | | jcli sprint list <boardId> | List sprints for a board | | jcli sprint list <boardId> --state active | Filter by state | | jcli sprint issues <sprintId> | List issues in a sprint |

Output

All output is JSON. Pipe to jq for filtering:

# Get just issue keys
jcli issue mine | jq '.issues[].key'

# Count by status
jcli issue mine --max 100 | jq '.issues | group_by(.status) | map({status: .[0].status, count: length})'

License

MIT