Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for teams that already keep product or engineering decisions in Markdown and want those decisions to become enforceable agent context instead of another stale docs folder.
Who should use it
Who should skip it
Consider itsthelore/rac-core lower priority if you already have a working solution in this category.
About this signal
itsthelore/rac-core is tracked by RepoRadar as a developer tool in the Knowledge / MCP section. It was first seen on 2026-07-01 and last updated on 2026-07-01. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Across RepoRadar's eight signals, itsthelore/rac-core is strongest on workflow potential (9.9) and open-source/build quality (8.4) and weakest on setup ease (6.4) — 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 itsthelore/rac-core a composite score of 8.4 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 vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
It serves requirements, decisions, prompts, and designs to agents over MCP, so keep its corpus inside the same review and access boundary you would use for source code; The system is only as current as the artifacts humans maintain, so stale ADRs or superseded decisions can still be enforced confidently unless your team keeps the corpus fresh.