github.com/fulldump/apitestGo

Verdict

Finished, not abandoned

github.com/fulldump/apitest looks complete rather than neglected — last commit 13 days ago. there are no open issues. A library that has stopped changing is not the same as one that has been dropped.

health 88/100

Why this verdict?

finished — No commits for over 365 days, and almost nobody filing new issues — or the README says the project is done.

last commit 615 days ago
almost no new issues — nobody is waiting on a fix

Judged yesterday from signal heuristics. How each verdict is decided

latest v1.3.1
stars 3
assessment attempted yesterday
GitHub evidence observed yesterday
registry checked 17 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 →

Came back

After 21 months without a release, github.com/fulldump/apitest published v1.3.1 on 2026-10-25.

Usually this is a maintainer returning. It is also what a hijacked package looks like, so it is worth a glance at what changed before you upgrade.

Maintenance trends

Loading historical repository activity…

Signals · last 2 checks

Commits 90d

Open issues

Unanswered

Contributors

State history 1

When	Change
2026-11-07	first verdict: finished

Badge

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

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

Watch it

Get told when github.com/fulldump/apitest 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.