minitest-reportersRubyGems · Ruby

Verdict

Quiet, but healthy

minitest-reporters has been quiet — no commits for 5 months, but nothing suggests trouble: 6 of 11 open issues have had no reply. This is a settled project, not a stalled one.

health 72/100

Why this verdict?

coasting — No commits for 90–365 days, with nothing else deteriorating.

last commit 157 days ago

Judged today from signal heuristics. How each verdict is decided

latest 1.8.0
licence MIT
stars 771
checked today
registry ↗
repository ↗

Vulnerabilities, end of life and next steps

Check a specific version for known advisories, documented mitigations and evidence-backed earlier-version options. Maintenance health is separate from vulnerability status.

Review remediation options →

Maintenance trends

Loading historical repository activity…

Signals · last 2 checks

Commits 90d

Open issues

Unanswered

Contributors

What the project says about itself

Open milestones — 0.X 3/3 done; 1.0.x 6/6 done. Source: the repository's milestones.
OpenSSF Scorecard — 3.4 / 10 on 2026-08-24. Source: OpenSSF, via deps.dev. A third party's view of security practice, not part of the health score.

Third-party facts checked yesterday; registry facts on every crawl.

State history 1

When	Change
2026-09-09	first verdict: coasting

Badge

Drop this in your README. It re-renders itself as the verdict changes.

[![maintenance](https://isitdeadyet.dev/badge/rubygems/minitest-reporters.svg)](https://isitdeadyet.dev/rubygems/minitest-reporters)

Watch it

Get told when minitest-reporters changes state, changes licence, or is deprecated — instead of finding out during an incident.

Free for up to 25 packages. Signing in is a link sent to your email — there is no password to choose.