github.com/m3db/m3clusterGo
- latest v0.0.0-20181017201615-3b9dd4710f09
- last known licence Apache-2.0
- stars 4,908
- assessment attempted 25 days ago
- GitHub evidence observed 25 days ago
- registry checked 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 →Moved
The registry still points at m3db/m3cluster, which is archived with a note saying development moved to m3db/m3. The verdict above is about the new home.
Maintenance trends
Loading historical repository activity…
Signals · last 2 checks
What the project says about itself
- Open milestones — 0.2.0 3/3 done; 0.1.0 4/4 done. Source: the repository's milestones.
- OpenSSF Scorecard — 3.3 / 10 on 2026-08-24. Source: OpenSSF, via deps.dev. A third party's view of security practice, not part of the health score.
Third-party facts checked 25 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-26 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/go/github.com/m3db/m3cluster)
Watch it
Get told when github.com/m3db/m3cluster 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.