Maintenance status — is the project effectively soft-archived?

Hi JJ — thanks for blessed. Ten years on, it's still the foundation under most Node TUI work (11k+ stars and meaningful downstream use including react-blessed, blessed-contrib, neo-blessed, and a long tail of CLI tools).

Asking before duplicating effort downstream:

What we're seeing:

• Last commit on master was 2016-01-04 (PR #214).
• The repo isn't archived, and neo-blessed (Embark Labs' fork) appears to be the most active continuation, though it's also slowed.

Two questions:

1. Is the project still being maintained in any form, or effectively in soft-archive mode? Knowing the answer helps downstream projects (react-blessed, blessed-contrib, our own CLI tooling) plan.
2. If contributions are welcome, would you take PRs for: modernizing dependencies, fixing the longest-standing reproducible issues, and getting a release out? Or is the working assumption now that maintenance has moved to forks (neo-blessed, etc.)?

If the project is in soft-archive mode, completely fair — we'll align with whichever fork is being actively maintained. We'd just rather upstream the work if you'd take it.

Context on who's asking: we use blessed via react-blessed in production CLI tooling for the Infernet Protocol (GPU compute marketplace). Happy to put real time in if there's a path to it landing upstream.

Thanks for the project's existence — it shaped the Node TUI space.