Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for teams that want a filesystem-shaped memory surface for agents, but do not want to hand-roll indexing, retrieval, and sync for every file type.
Who should use it
Who should skip it
Skip supermemoryai/smfs if the source link, documentation, or setup requirements do not align with your current workflow or stack.
About this signal
supermemoryai/smfs is tracked by RepoRadar as a infrastructure tool in the AI Infrastructure section. It was first seen on 2026-06-28 and last updated on 2026-06-28. The current verdict is 'try now' with a Silver tier and moderate setup difficulty. The standout signals for supermemoryai/smfs are workflow potential (9.0) and open-source/build quality (8.4), while momentum (4.0) 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 supermemoryai/smfs 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 2.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
Normal use requires a Supermemory API key and hosted service account, so this is not a fully local memory layer even when it mounts like one; Mounted memory can expose sensitive files to semantic indexing and sync, so start with a narrow allowlist instead of your whole workspace; The default install path uses a remote shell script, which should be reviewed before use in a production environment.