battlecommand-forgecrates.io

Verdict

Looks abandoned

battlecommand-forge appears abandoned — its repository has been archived, last commit 17 days ago. There are no open issues. 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.

repository archived

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

latest 0.2.0
last known licence Apache-2.0
stars 1
assessment attempted 14 days ago
GitHub evidence observed 14 days ago
registry checked 20 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 2 checks

Commits 90d

Open issues

Unanswered

Contributors

What the project says about itself

Security policy — published. Source: the repository.

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

State history 2

When	Change
2026-10-27	coasting → abandoned
2026-09-27	first verdict: coasting

Badge

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

[![maintenance](https://isitdeadyet.dev/badge/crates/battlecommand-forge.svg)](https://isitdeadyet.dev/crates/battlecommand-forge)

Watch it

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