Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for developers and AI platform teams that want a compact local memory or retrieval layer they can actually embed, benchmark, and ship without defaulting to a hosted database.
Who should use it
Who should skip it
Move on from Egoist-Machines/LodeDB if the licensing terms, language support, or platform requirements do not fit your project.
About this signal
Egoist-Machines/LodeDB is tracked by RepoRadar as a vector database in the Model Infrastructure section. It was first seen on 2026-06-29 and last updated on 2026-06-29. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Across RepoRadar's eight signals, Egoist-Machines/LodeDB is strongest on workflow potential (9.4) and practical usefulness (9.0) and weakest on momentum (6.0) — a profile worth weighing against your own priorities. 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 Egoist-Machines/LodeDB a composite score of 8.3 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 18.0 and never affects the composite score or tier. The risk label of 'none' 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
Installing the optional MCP server turns the local store into a memory surface other agent clients can query, so scope the database path and permissions before connecting it to coding tools.
