Item detail
github.com

ardhaecosystem/synapse

RepoRadar surfaced ardhaecosystem/synapse — an agent project — into the Developer Tools section, where it sits at Gold tier with a 'try now' verdict. Its strongest signal is workflow potential, scored 9.6 out of 10.

Score8.1
Popularity8.0
Riskconditional
TierGold
Score breakdown
Usefulness8.0
Novelty9.0
Momentum5.0
Maturity6.1
Open-source/build8.4
Evidence8.0
Workflow potential9.6
Setup ease4.2

Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.

Why it matters

Useful for agent builders who want a richer memory model than a plain markdown file or vector store, especially when they need self-hosted storage and time-aware recall.

Who should use it

Hermes Agent users who want a richer self-hosted memory provider than native markdown memory Agent platform builders evaluating temporal memory graphs and salience-based retention Teams that need point-in-time memory queries instead of only current-state recall Developers experimenting with Graphiti and FalkorDB for long-running agent systems

Who should skip it

Hold off on ardhaecosystem/synapse if the setup requirements exceed what your current workflow or team can support without dedicated engineering time.

About this signal

ardhaecosystem/synapse is tracked by RepoRadar as an agent project in the Developer Tools section. First seen 2026-06-29; the source record was last checked on 2026-06-29. The current verdict is 'try now' with a Gold tier and hard setup difficulty. ardhaecosystem/synapse leads on workflow potential (9.6) and novelty (9.0); its lowest signal is setup ease (4.2), so factor that in before investing setup time. 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 ardhaecosystem/synapse record combines a 8.1/10 composite score with separate popularity (8.0), risk (conditional), and setup (hard) signals. See the scoring methodology for the current weights and evidence definitions.

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 user and project memory in a self-hosted graph database and can send extracted memory context to an OpenAI-compatible model backend, so start with non-sensitive conversations and a controlled provider setup.

Evidence links
Closest alternatives / related signals
agent-memory knowledge-graph hermes-agent falkordb graphrag mit
Verification record

What RepoRadar actually verified

Discovered

Automated discovery and source capture. Last checked 2026-08-13T20:20:15Z.

No editorial or hands-on review is claimed. This record remains at Discovered.

Verification sources

Longitudinal intelligence

How this decision record is moving

Raw history JSON →

36 dated snapshots retained from 2026-06-29 through 2026-08-13; see the snapshot index for explicit coverage gaps. Stars, version, release, pricing, integration, risk, maintenance, verdict, score, and momentum fields remain explicit even when a source has not reported them. Repository momentum is a normalized 0–10 RepoRadar signal; GitHub stars appear only where the popularity monitor retained exact timestamped observations.

RepoRadar score8.1 current · +0.0 net
Repository momentum9.0 current · +4.0 net
GitHub stars (observed)74 current · +4 net
GitHub stars74 exact observation
VersionNot reported by source
Last releaseNot reported by source
Maintenanceactive
Current riskconditional
Current verdicttry now
Pricing baselineNo structured commercial pricing baseline
Pricing checkedNot applicable or not recorded
Pricing freshnessNo dated commercial pricing review
Integrations baselineNo structured integrations recorded

Recent dated points

DateScoreMomentumStarsRiskVerdictMaintenance
2026-08-138.19.074conditionaltry nowactive
2026-08-128.19.073conditionaltry nowactive
2026-08-118.19.073conditionaltry nowactive
2026-08-108.19.073conditionaltry nowactive
2026-08-098.19.073conditionaltry nowactive
2026-08-088.19.073conditionaltry nowactive
2026-08-078.19.073conditionaltry nowactive
2026-08-068.15.0Not recordedconditionaltry nownot recorded
2026-08-058.15.0Not recordedconditionaltry nownot recorded
2026-08-048.19.073conditionaltry nowactive
2026-08-038.19.073conditionaltry nowactive
2026-08-028.19.072conditionaltry nowactive

Why the record changed

stars changed

Stars changed: 73 → 74.

stars changed

Stars changed: 72 → 73.

stars changed

Stars changed: 71 → 72.

stars changed

Stars changed: 70 → 71.