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.
Where this stands now
memforks-dev/memforks ranks #3 of 7 tracked Agent Memory items by composite score (8.2 against a section median of 8.2). The section currently carries 4 Silver, 3 Gold. RepoRadar has retained observations for this record since 2026-06-28 (104 days in the current window).
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. First seen 2026-06-28; the source record was last checked 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 public evidence on the linked source page and states where additional review is still needed.
How this item is evaluated
The memforks-dev/memforks record combines a 8.2/10 composite score with separate popularity (1.0), risk (conditional), and setup (moderate) signals. See the scoring methodology for the current weights and evidence definitions.
Questions worth asking before you adopt this
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.