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-crashlytics

v0.1.3

Published

Mushi Mushi plugin for Firebase Crashlytics — flags fixed reports via Remote Config and closes Crashlytics issues when Mushi applies a fix.

Readme

@mushi-mushi/plugin-crashlytics

Mushi Mushi plugin: when Mushi marks a report fixed, close the matching Crashlytics issue (and write a Remote Config marker so the mobile client can short-circuit duplicate reports).

Install

npm i @mushi-mushi/plugin-crashlytics

Run as a stand-alone server

MUSHI_PLUGIN_SECRET=...                # set when the plugin is installed in Mushi admin
GOOGLE_OAUTH_BEARER=...                # short-lived Google OAuth2 access token
FIREBASE_PROJECT_ID=...                # Firebase project id
PORT=3000                              # optional
npx mushi-plugin-crashlytics

Issue an OAuth2 bearer with the https://www.googleapis.com/auth/firebase scope and refresh it via your service-account workflow before each run.

Programmatic usage

import { createCrashlyticsPlugin } from '@mushi-mushi/plugin-crashlytics'
import express from 'express'
import { expressMiddleware } from '@mushi-mushi/plugin-sdk'

const handler = createCrashlyticsPlugin({
  bearer: process.env.GOOGLE_OAUTH_BEARER!,
  projectId: process.env.FIREBASE_PROJECT_ID!,
  mushiSecret: process.env.MUSHI_PLUGIN_SECRET!,
})

express().post('/mushi/webhook', expressMiddleware(handler)).listen(3000)

Subscribed events

  • fix.applied
    • Remote Config: PATCH mushi_resolved_{reportId} = true so the mobile SDK can suppress duplicate reports for the same root cause.
    • Crashlytics v1alpha: PATCH the issue to state: CLOSED.

Notes

  • The plugin is outbound-only; for inbound Crashlytics → Mushi ingestion use the Crashlytics adapter in @mushi-mushi/adapters.
  • Bearer token refresh is the caller's responsibility — design assumes the process runs behind a service-account refresher (Google ADC, IAM Workload Identity).

License

MIT