specflow.allureNuGet · C# / .NET

Verdict

Looks abandoned

specflow.allure appears abandoned — last commit 32 days ago. 30 of 55 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 3.5.0.73
stars 126
assessment attempted today
GitHub evidence observed 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 1 check

The first observation is recorded. Trend lines appear once at least two checks have data for the same signal.

Commits 90d

Open issues

Unanswered

Contributors

What the project says about itself

Open milestones — Remove deprecated .NET versions; Rework SpecFlow integration 1/1 done; Unify Steps context for XUnit and NUnit; Improve stability. Source: the repository's milestones.

Third-party facts checked today; registry facts on every crawl.

State history 1

When	Change
2026-10-19	first verdict: abandoned

Badge

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

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

Watch it

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