container-speccrates.io

Verdict

Not enough signal to judge

We could not find enough public signal to judge container-spec — no repository resolved from its registry metadata.

health 29/100

Why this verdict?

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

no repository resolved from registry metadata; last release 2448 days ago

Judged yesterday from signal heuristics. How each verdict is decided

latest 1.0.1
licence Apache-2.0
assessment attempted yesterday
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

—

State history 1

When	Change
2026-10-17	first verdict: unknown

Badge

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

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

Watch it

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