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

@mushi-mushi/plugin-jira

v0.2.2

Published

First-party Jira plugin for Mushi Mushi — OAuth 2.0 (3LO) connect flow, bidirectional sync (create issues from reports, mirror status changes back), and Jira webhook handler.

Readme

@mushi-mushi/plugin-jira

Bidirectional sync between Mushi Mushi reports and Jira Cloud issues. Creates issues on report.created, updates them on report.classified, transitions status on report.status_changed, and comments fix summaries on fix.applied.

Install

npm i @mushi-mushi/plugin-jira

OAuth setup (one-time per tenant)

  1. Create a Jira Cloud OAuth 2.0 (3LO) app at developer.atlassian.com.
  2. Enable the read:jira-work, write:jira-work, and offline_access scopes.
  3. Set the callback URL to https://<your-plugin-host>/oauth/jira/callback.
  4. Stash the client ID + secret as env vars.
import { buildAuthorizeUrl, exchangeCode, refreshTokens } from '@mushi-mushi/plugin-jira'

const config = {
  clientId: process.env.JIRA_CLIENT_ID!,
  clientSecret: process.env.JIRA_CLIENT_SECRET!,
  redirectUri: process.env.JIRA_REDIRECT_URI!,
  scopes: ['read:jira-work', 'write:jira-work', 'offline_access'],
}

// 1. Redirect the user to Jira to authorize.
const { url, state, codeVerifier } = buildAuthorizeUrl(config, projectId)

// 2. On callback, exchange `code` for tokens and store them.
const tokens = await exchangeCode(config, code, codeVerifier)

Tokens are short-lived — call refreshTokens(config, tokens.refreshToken) before expiry, or persist the mapping and refresh lazily on 401.

Wire up the webhook handler

import express from 'express'
import { createJiraPluginHandler } from '@mushi-mushi/plugin-jira'
import { expressMiddleware } from '@mushi-mushi/plugin-sdk'

const handler = createJiraPluginHandler({
  secret: process.env.MUSHI_PLUGIN_SECRET!,
  tokens: loadTokensForTenant(),      // you persist these after OAuth
  jiraProjectKey: 'BUG',
  statusToTransition: {
    pending: 'To Do',
    fixing: 'In Progress',
    fixed: 'Done',
  },
})

const app = express()
app.post('/mushi/webhook', expressMiddleware(handler))

Subscribed events

| Event | Effect on Jira | | ------------------------- | ------------------------------------------------------------------ | | report.created | Creates a Jira issue under jiraProjectKey with mushi labels. | | report.status_changed | Transitions the issue via statusToTransition map. | | fix.applied | Adds a comment linking the GitHub PR (or fix summary). |

Other Mushi events are ignored — add them to the on map to customize.

Status mapping defaults

| Mushi status | Jira transition | | -------------- | ----------------- | | pending | To Do | | classified | To Do | | grouped | To Do | | fixing | In Progress | | fixed | Done | | dismissed | Done |

Override any mapping via the statusToTransition option.

License

MIT