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

verifone-jira-reporter

v1.0.3

Published

Basic tool to report a bug in Jira when a test fails

Readme

Installation

Run following command to install package via npm

npm install @verifone/verifone-jira-reporter

How it works?

  • It creates a Jira epic for every test run if the epic id is not passed in configuration
  • Create bugs for all failed test cases based on the test case severity i.e. the bug report level (configurable)
  • Links every bug to the epic
severity values

[critical, high, medium, low, all]

critical Bugs will be created for tests that are having severity critical

high Bugs will be created for tests that are having severity [critical | high]

medium Bugs will be created for tests that are having severity [critical | high | medium]

low - Bugs will be created for tests that are having severity [critical | high | medium | low]

all - Bugs will be created for failed tests

Bug Details

It creates bugs for the failed tests after all tests are executed, currently only following details are added for the bug

  • Epic - epic id, tool creates a new pic if there is not epic id in configuration
  • Summery - Bug summery
  • Description - Bug Description along with failed test case details
  • Assignee - User to be assigned
  • Screenshot - Attaches test failure screenshot

Authentication

Currently this tools supports following two forms of authentication Basic Authentication and Basic Authentication With API Token

User will require to specify the Jira credentials or token in configuration file

You can configure this reporter in following way to any project

    ReportConfig = {
        jira:{
            autoCreteBugOnTestFailure:true,
            host: "https://autodemojira.atlassian.net",
            user: "[email protected]",
            password: "xxxxx",
            projectKey: "PAG" //Unique key for every project
        }
}