minitarRubyGems · Ruby

Verdict

Quiet, but healthy

minitar has been quiet — no commits for 4 months, but nothing suggests trouble: there are no open issues. This is a settled project, not a stalled one.

health 84/100

Why this verdict?

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

last commit 130 days ago

Judged today from signal heuristics. How each verdict is decided

latest 1.1.0
licence Ruby OR BSD-2-Clause
stars 45
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

Security policy — published. Source: the repository.
Open milestones — 1.0 (due 2016-12-31) 6/6 done. Source: the repository's milestones.

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/minitar.svg)](https://isitdeadyet.dev/rubygems/minitar)

Watch it

Get told when minitar 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.