Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for developers onboarding to unfamiliar codebases or turning architecture edits into concrete Claude Code tasks without reconstructing the dependency graph by hand.
Who should use it
Who should skip it
Move on from srihari7070/lore-map if the licensing terms, language support, or platform requirements do not fit your project.
About this signal
srihari7070/lore-map is tracked by RepoRadar as a architecture mapper in the Developer Workflow section. It was first seen on 2026-06-30 and last updated on 2026-06-30. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Across RepoRadar's eight signals, srihari7070/lore-map is strongest on workflow potential (9.7) and open-source/build quality (8.4) and weakest on momentum (5.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 srihari7070/lore-map a composite score of 8.2 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 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 evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
Deep-scan and build flows can send real source structure to Claude on your own subscription, so first run should stay on non-sensitive repos until the prompt surface is clear; The tool can progress from map edits into code-writing actions, so review the generated instruction and keep changes on throwaway branches during the first cycle.