github.com/google/mtailGo

Verdict

Looks abandoned

github.com/google/mtail appears abandoned — its repository has been archived, no commits for 8 months. 8 of 43 open issues have had no reply. Plan a migration rather than waiting for a fix.

health 10/100

Why this verdict?

abandoned — No commits for over 365 days with unanswered issues piling up — or the registry marks it deprecated, or the repository is archived.

repository archived

Judged 13 days ago from signal heuristics. How each verdict is decided

latest v0.0.0-20260226175936-4c7e0e1174ac
last known licence Apache-2.0
stars 4,033
assessment attempted 13 days ago
GitHub evidence observed 13 days ago
registry checked 18 days ago
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 — 3.0.0 2/4 done. Source: the repository's milestones.
OpenSSF Scorecard — 5.9 / 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 13 days ago; registry facts on every crawl.

State history 2

When	Change
2026-10-24	coasting → abandoned
2026-09-24	first verdict: coasting

Badge

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

[![maintenance](https://isitdeadyet.dev/badge/go/github.com/google/mtail.svg)](https://isitdeadyet.dev/go/github.com/google/mtail)

Watch it

Get told when github.com/google/mtail 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.