Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for developers and teams who want to understand which repos and sessions are actually burning tokens before AI coding spend turns into a vague monthly bill.
Who should use it
Who should skip it
Skip mehmetdemircs/RepoSpend if the source repository or demo is inactive, unmaintained, or no longer matches the description shown here.
About this signal
mehmetdemircs/RepoSpend is tracked by RepoRadar as a developer tool in the AI Ops section. It was first seen on 2026-06-27 and last updated on 2026-06-27. The current verdict is 'try now' with a Silver tier and easy setup difficulty. The standout signals for mehmetdemircs/RepoSpend are workflow potential (8.8) and setup ease (8.8), 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 mehmetdemircs/RepoSpend a composite score of 7.7 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 9.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
The dashboard reads local usage files and can expose repo names, session metadata, and model usage to anyone who can access the machine or browser session; Its spend numbers are API-equivalent estimates rather than exact provider invoices, so use it as an operational signal not a billing source of truth; Support depth still varies by tool, with Codex strongest today and Claude Code, Copilot, and Cursor coverage less mature.