checkcrates.io

Verdict

Not enough signal to judge

check is developed on codeberg.org, which we do not read yet, so there is no commit or issue signal to judge it by. That is a limit of ours, not a verdict on the package.

health 46/100

Why this verdict?

unknown — No repository resolved from the registry metadata, and no recent release either.

repository is on codeberg.org, which we do not read yet; last release 1668 days ago

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

latest 1.0.0
licence MIT OR Apache-2.0
assessment attempted 8 days ago
registry ↗

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

—

State history 1

When	Change
2026-10-10	first verdict: unknown

Licence history 1

When	Change	Severity
2026-10-10	MIT → MIT OR Apache-2.0 (1.0.0)	info

Badge

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

[![maintenance](https://isitdeadyet.dev/badge/crates/check.svg)](https://isitdeadyet.dev/crates/check)

Watch it

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