Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for people who want one local retrieval layer that both humans and agents can query from the terminal or through MCP instead of stitching together several separate indexing tools.
Who should use it
Who should skip it
Skip timorunge/lore unless the captured evidence suggests it solves a problem you are actively working on.
About this signal
timorunge/lore is tracked by RepoRadar as a developer tool in the Agent Knowledge section. It was first seen on 2026-07-01 and last updated on 2026-07-01. The current verdict is 'try now' with a Silver tier and easy setup difficulty. timorunge/lore leads on workflow potential (9.3) and setup ease (8.8); its lowest signal is maturity (5.7), so factor that in before investing setup time. 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 timorunge/lore a composite score of 7.8 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 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
It can ingest email, shell commands, and other sensitive local sources, so the first evaluation should use a narrowly scoped store rather than a whole machine snapshot; Windows users currently need WSL for the easiest path because prebuilt binaries are documented for Linux and macOS first.