Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for builders who want a memory system they can inspect, benchmark, and self-host locally before trusting an agent with cross-session recall.
Who should use it
Who should skip it
Skip vornicx/Midas unless the captured evidence suggests it solves a problem you are actively working on.
About this signal
vornicx/Midas is tracked by RepoRadar as a agent memory in the AI Infrastructure section. It was first seen on 2026-06-30 and last updated on 2026-06-30. The current verdict is 'worth watch' with a Silver tier and advanced setup difficulty. Across RepoRadar's eight signals, vornicx/Midas is strongest on open-source/build quality (8.4) and workflow potential (8.3) and weakest on momentum (4.0) — a profile worth weighing against your own priorities. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned vornicx/Midas a composite score of 7.9 out of 10, placing it in the Silver tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 1.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
It stores cross-session memory that may later influence agent decisions, so validate the stale-memory and confirmation guards before letting it steer real tools or external systems; The benchmark story is strong for an early project, but the repo is still young enough that most teams should treat it as an evaluated component rather than a production default.