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 🙏

© 2025 – Pkg Stats / Ryan Hefner

git-ticket

v0.4.2

Published

Get JIRA ticket info from the Git commit log

Downloads

43

Readme

git-ticket Build Status npm version

Get JIRA tickets from the Git commit log.

Supported actions are:

  • listing JIRA tickets from Git commit messages
  • listing JIRA tickets and retrieving summary info from JIRA
  • adding fix versions in JIRA for all found tickets

To install:

$ npm install git-ticket

List tickets from Git commit message

To retrieve all JIRA tickets that are present in commit messages starting from the previous tag (automatically determined) until Git tag version 0.2:

$ get-ticket list 0.2
Listing from 0.1 to 0.2
JIRA-1

JIRA ticket numbers are written to standard output.

List tickets and retrieve summary info from JIRA

The JIRA ticket summary can be automatically when a JIRA configuration file is found. Either use the default .jiraconfig or pass a custom file using the --jira-config option:

$ get-ticket ls 0.2.1 --jira-config jira_example_config.json
Listing from 0.2 to 0.2.1
GIT-1 First test story
GIT-2
JIRA-1

The JSON file contains the Jira connection details and authentication credentials to use, see jira_example_config.json and https://www.npmjs.com/package/jira-connector for details.

Add fix version in JIRA

To add fix version 0.2.1 for all tickets found from the latest tag 0.2.1:

$ git-ticket add 0.2.1
Adding fix-version 0.2.1, from 0.2 to 0.2.1
GIT-1 0.2, 0.2.1
GIT-2 0.2.1

By default the to tag is used a fix version value, to override use the --fix-version option.

Line colors mean:

  • green: no update needed, already has fix version
  • yellow: added fix version
  • red: failed to update fix version

Automatically determining the previous tag

The previous tag is determined by using git describe, it finds the first matching tag from the given to tag. Only tags that match the following semantic versioning regex [0-9]*\.[0-9]*\.[0-9]* are used.