Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for heavy coding-agent users who want a cleaner way to repair bad context, compare sessions, and manage local memory layers across multiple agent tools without depending on vendor UX.
Who should use it
Who should skip it
Skip voidcraft-dev/memory-forge-rs unless the captured evidence suggests it solves a problem you are actively working on.
About this signal
voidcraft-dev/memory-forge-rs is tracked by RepoRadar as a developer tool in the Knowledge / Memory section. It was first seen on 2026-07-01 and last updated on 2026-07-01. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. The standout signals for voidcraft-dev/memory-forge-rs are workflow potential (9.1) and open-source/build quality (8.4), while maturity (6.3) trails — that balance shapes where it fits best. 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 voidcraft-dev/memory-forge-rs a composite score of 8.0 out of 10, placing it in the Gold 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 evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
Editing stored agent memory can make later outputs harder to audit unless teams keep the original session history and treat memory edits as deliberate interventions; The tool works with local session caches that may contain proprietary code, prompts, or notes, so first use should stay inside a low-sensitivity project with backups.