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

seniore

v6.0.0

Published

Gracefully manage your GitHub and Jira workflow

Downloads

6

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

p2kmgclp2kmgcl

Keywords

githubjiraworkflowcliliferay

Readme

Custom list of github and jira related commands currently customized to behave as an ordinary Liferay workflow.

About username parameter: in Liferay, we make PRs to forked repos instead of using the upstream repository. Because of this, if username is not specified in some command, it defaults to the origin remote instead of upstream.

CLI Interface

Options:
  --verbose-error                             show full stack trace when a fatal error occurs
  -V, --version                               output the version number
  -h, --help                                  display help for command

Commands:
  init|i [options]                            initialize config file
  checkout-pull-request|c [options] <number>  checkout specified PR
  send-pull-request|s [options] <username>    send current branch as PR
  list-issues|li <boardId>                    list JIRA board issues
  list-pull-requests|lp [options]             list existing pull requests
  list-notifications|ln [options]             list GitHub notifications

Configuration

JSON Schema

github.token

GitHub token. Needed permissions may vary depending on the commands that are being used (for example, there is no need to have a token in order to checkout a pull request, but necessary if you are creating a new one). API rate limit may vary depending on the token too (see GitHub API documentation).

jira

JIRA configuration. If host is not specified, JIRA functionality is simply ignored when using mixed GitHub/JIRA commands (like sending pull requests).

  • jira.host (only domain without protocol, for example myjira.server.com).
  • jira.username.
  • jira.password.

githubUserToJiraUser

Sometimes (for example, when sending pull requests), seniore can update related JIRA tickets, GitHub issues, pull requests, etc. These mappings help seniore know which JIRA user corresponds to each GitHub user.