Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for anyone juggling Claude Code, Codex, Cursor, Gemini CLI, Roo Code, Goose, and similar tools: it turns scattered usage logs into one readable local view so teams can spot cost drift before it becomes a budgeting problem.
Where this stands now
mm7894215/TokenTracker ranks #11 of 1508 tracked Radar items by composite score (8.9 against a section median of 7.8). The section currently carries 643 Gold, 443 Silver, 422 Bronze. RepoRadar has retained observations for this record since 2026-06-19 (88 days in the current window). Signal extremes versus the section: momentum at the 84th percentile.
Who should use it
Who should skip it
Skip mm7894215/TokenTracker unless the captured evidence suggests it solves a problem you are actively working on.
About this signal
mm7894215/TokenTracker is tracked by RepoRadar as a developer tool in the Radar section. First seen 2026-06-19; the source record was last checked on 2026-06-19. The current verdict is 'try now' with a Gold tier and easy setup difficulty. The standout signals for mm7894215/TokenTracker are workflow potential (10.0) and practical usefulness (9.0), while novelty (7.0) trails — that balance shapes where it fits best. This page summarizes the public evidence on the linked source page and states where additional review is still needed.
How this item is evaluated
The mm7894215/TokenTracker record combines a 8.9/10 composite score with separate popularity (85.0), risk (none), and setup (easy) signals. See the scoring methodology for the current weights and evidence definitions.
Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
No inherent user-impacting risk is flagged from the captured evidence.