Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for builders who need durable agent memory but want better isolation, rollback, and collaboration semantics than a single shared memory log can provide.
Who should use it
Who should skip it
Pass on memforks-dev/memforks if its scope or audience does not match what your team is building right now.
About this signal
memforks-dev/memforks is tracked by RepoRadar as a developer tool in the Agent Memory section. It was first seen on 2026-06-28 and last updated on 2026-06-28. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. The standout signals for memforks-dev/memforks are workflow potential (9.7) and open-source/build quality (8.4), while setup ease (6.4) 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 memforks-dev/memforks a composite score of 8.2 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 vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
The quick-start provisions keys, gas, and encrypted storage layers under the hood, so first evaluation should use throwaway credentials and a non-production memory tree; Shared memory branches can spread low-quality or overbroad context if teams merge too aggressively, so operators should treat memory review as part of the workflow instead of assuming every branch deserves promotion.