bonsai.scriptingNuGet · C# / .NET

Verdict

Looks abandoned

bonsai.scripting appears abandoned — no commits for 3 months. 224 of 342 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 21 days ago from signal heuristics. How each verdict is decided

latest 2.8.0
stars 199
assessment attempted 21 days ago
GitHub evidence observed 21 days ago
registry checked 21 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 3 checks

Commits 90d

Open issues

342

Unanswered

224

Contributors

What the project says about itself

Open milestones — 3.0 1/28 done; 2.9.2 (due 2026-09-30) 4/28 done; 2.10.0 (due 2026-12-31) 0/3 done. Source: the repository's milestones.

Third-party facts checked 24 days ago; registry facts on every crawl.

State history 1

When	Change
2026-10-20	first verdict: abandoned

Badge

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

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

Watch it

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