unitconversionNuGet · C# / .NET

Verdict

Finished, not abandoned

unitconversion looks complete rather than neglected — last commit this week. all 2 open issues have had a reply. A library that has stopped changing is not the same as one that has been dropped.

health 75/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 1913 days ago
almost no new issues — nobody is waiting on a fix

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

latest 2.0.0
last known licence MIT
stars 187
assessment attempted 9 days ago
GitHub evidence observed 9 days ago
registry checked 9 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 5 years without a release, unitconversion published 2.0.0 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-10-28	first verdict: finished

Badge

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

[![maintenance](https://isitdeadyet.dev/badge/nuget/unitconversion.svg)](https://isitdeadyet.dev/nuget/unitconversion)

Watch it

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