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

get-jj

v1.1.0

Published

JJ: your helpful jira buddy — a fast, friendly CLI for Jira Cloud

Readme

     ██╗      ██╗
     ██║      ██║   your helpful jira buddy
     ██║      ██║
██   ██║ ██   ██║
╚█████╔╝ ╚█████╔╝
 ╚════╝   ╚════╝

A fast, friendly CLI for Jira Cloud. Fetch tickets as markdown, manage your sprint board in the terminal, generate sprint summaries, and pipe everything into your AI coding agent.

Install

npm install -g get-jj

Setup

  1. Create a .env file in JJ's install directory, or set environment variables directly:
# Find where JJ was installed, then create .env there:
jj help  # shows install location in the banner

# Or just set env vars in your shell profile:
export JIRA_BASE_URL=https://yourcompany.atlassian.net
export [email protected]
export JIRA_API_TOKEN=your-token-here
export JIRA_PROJECT=WEB
export JIRA_BOARD_ID=36
  1. You'll need these credentials:
  • JIRA_BASE_URL — Your Jira Cloud URL (e.g., https://yourcompany.atlassian.net)
  • JIRA_EMAIL — Your Jira account email
  • JIRA_API_TOKEN — Generate one at Atlassian API Tokens
  • JIRA_PROJECT — Your project key (e.g., WEB, APP, ENG)
  • JIRA_BOARD_ID — Find it in your board URL: /jira/software/projects/WEB/boards/<ID>
  1. Verify it works:
jj list

Install from source

git clone https://github.com/jasperfurniss/jj.git
cd jj
npm install
npm run build
npm link
cp .env.example .env  # fill in your credentials

Commands

| Command | Description | |---------|-------------| | jj | Interactive: list issues, select, view as markdown | | jj <KEY> | Fetch a specific issue (e.g., jj WEB-1234) | | jj list | List your assigned sprint issues | | jj board | Interactive kanban board — move cards between columns | | jj sprint | Sprint overview — all team issues grouped by status | | jj sprint --by-person | Sprint overview grouped by person | | jj summary | Sprint roundup — auto-copies Slack-formatted summary to clipboard | | jj summary --concise | Shorter format for quick updates | | jj ready <number> | Transition an issue to Review (e.g., jj ready 1234) | | jj open <KEY> | Open issue in browser | | jj comment <KEY> | Post a comment (-m "msg" or opens $EDITOR) | | jj create | Create an issue (-m, $EDITOR, or pipe from stdin) | | jj clone <KEY> | Clone an issue (keeps type, parent, labels) | | jj whois <name> | What's assigned to this person? | | jj search <text> | Search issues by summary | | jj help | Show all commands |

Most commands support --pipe for non-interactive, machine-readable output.

For Product Managers

JJ is built for developers and PMs. The sprint management commands are designed for the weekly rhythm of managing a Jira board:

  • jj summary — The big one. Generates a Slack-ready sprint roundup covering the entire team: Sprint Focus, PTO Radar, Agenda Highlights, Key Milestones, and Primary Focus Areas broken out by person. Automatically copies to your clipboard in Slack format — just paste into your squad channel and fill in the PTO days, milestones, and commentary. Use --concise for a shorter version.
  • jj sprint — Full sprint snapshot showing all team issues grouped by status. Use --by-person to see what each person is working on.
  • jj whois <name> — Check someone's plate before standup or 1:1s.
  • jj board — Full kanban board in your terminal. Drag cards between columns with keyboard or mouse.

Agent Integration

JJ comes with agent skills that make working with Jira a breeze in AI coding assistants.

JJ's --pipe mode outputs clean markdown to stdout, making it a perfect tool for AI agents. When your agent sees a Jira issue key like WEB-1234, it can automatically fetch the full ticket context.

Cursor

Copy the rule into your Cursor config:

cp skills/cursor-rule.mdc ~/.cursor/rules/jj.mdc

Now when you mention a Jira key in Cursor, it'll fetch the ticket automatically.

Claude Code

Append the skill to your project's CLAUDE.md (or global ~/.claude/CLAUDE.md):

cat skills/claude-code.md >> CLAUDE.md

Configuration

All configuration is via environment variables in .env. See .env.example for the full list.

Optional settings

| Variable | Default | Description | |----------|---------|-------------| | JIRA_DEFAULT_JQL | Current user's open sprint | Default query for jj list | | JIRA_OUTPUT_DIR | ./jira-output | Where downloaded attachments go | | JJ_READY_TRANSITION | REVIEW | Transition name for jj ready | | JJ_COLUMNS | ["To Do","In Progress","Review","Done"] | Board column names (JSON) | | JJ_STATUS_MAP | See .env.example | Status-to-column mapping (JSON) | | JJ_COLUMN_TRANSITIONS | See .env.example | Transition name candidates (JSON) |

License

MIT