ad4mcrates.io
- latest 0.9.0
- last known licence CAL-1.0
- stars 100
- assessment attempted 23 days ago
- GitHub evidence observed 23 days ago
- registry checked 29 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
100
Open issues
258
Unanswered
170
Contributors
6
What the project says about itself
- Open milestones — ADAM Executor Hosting service (due 2024-05-25) 3/6 done; Sybil-prevention (due 2024-07-01); AD4M Launcher 1.0 (due 2024-08-31) 22/38 done; Social Organisms, aka DAO Tooling (due 2024-10-15) 0/2 done; Developer tooling (due 2024-12-01) 5/14 done. Source: the repository's milestones.
Third-party facts checked 23 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-24 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/crates/ad4m)
Watch it
Get told when ad4m 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.