fakeNuGet · C# / .NET

Verdict

Looks abandoned

fake appears abandoned — no commits for 2 months. 6 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.

registry marks the package deprecated

Judged today from signal heuristics. How each verdict is decided

latest 5.16.0
stars 1,325
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 — 3.0 1/1 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-12	first verdict: abandoned

Where to go instead 1

local

Named by the maintainers in the deprecation notice

Please use local or global tools and follow the migration guide https://fake.build/guide/fake-migrate-to-fake-5.html

From the maintainers’ own deprecation notice.

Badge

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

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

Watch it

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