Item detail
github.com

mm7894215/TokenTracker

RepoRadar surfaced mm7894215/TokenTracker — a developer tool — into the Radar section, where it sits at Gold tier with a 'try now' verdict. Its strongest signal is workflow potential, scored 10.0 out of 10.

Score8.9
Popularity85.0
Risknone
TierGold
Score breakdown
Usefulness9.0
Novelty7.0
Momentum9.0
Maturity8.7
Open-source/build8.4
Evidence7.2
Workflow potential10.0
Setup ease8.8

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.

Who should use it

AI coding-tool users engineering managers freelancers tracking model spend teams comparing coding assistants

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. It was first seen on 2026-06-19 and last updated 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. 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 mm7894215/TokenTracker a composite score of 8.9 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 85.0 and never affects the composite score or tier. The risk label of 'none' 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

No inherent user-impacting risk is flagged from the captured evidence.

Evidence links
Closest alternatives / related signals
token-tracking cost-observability ai-coding local-first developer-tools
Verification record

What RepoRadar actually verified

Discovered

Automated discovery and source capture. Last checked 2026-08-03T18:56:10Z.

No editorial or hands-on review is claimed. This record remains at Discovered.

Verification sources

Longitudinal intelligence

How this decision record is moving

Raw history JSON →

36 dated snapshots retained from 2026-06-19 through 2026-08-03; see the snapshot index for explicit coverage gaps. Stars, version, release, pricing, integration, risk, maintenance, verdict, score, and momentum fields remain explicit even when a source has not reported them. Repository momentum is a normalized 0–10 RepoRadar signal; GitHub stars appear only where the popularity monitor retained exact timestamped observations.

RepoRadar score8.9 current · +0.0 net
Repository momentum9.3 current · +0.3 net
GitHub stars (observed)1,171 current · +195 net
GitHub stars1,171 exact observation
Versionv0.87.11
Last release2026-08-02T16:32:09Z
Maintenanceactive
Current risknone
Current verdicttry now
Pricing baselineNo structured commercial pricing baseline
Pricing checkedNot applicable or not recorded
Pricing freshnessNo dated commercial pricing review
Integrations baselineClaude Code

Recent dated points

DateScoreMomentumStarsRiskVerdictMaintenance
2026-08-038.99.31,171nonetry nowactive
2026-08-028.99.31,161nonetry nowactive
2026-08-018.99.01,152nonetry nowactive
2026-07-318.99.0Not recordednonetry nownot recorded
2026-07-308.99.0Not recordednonetry nownot recorded
2026-07-298.99.31,124nonetry nowactive
2026-07-288.99.01,116nonetry nowactive
2026-07-218.99.01,029nonetry nowactive
2026-07-208.99.01,029nonetry nowactive
2026-07-198.99.01,029nonetry nowactive
2026-07-188.99.01,029nonetry nowactive
2026-07-178.99.01,029nonetry nowactive

Why the record changed

stars changed

Stars changed: 1161 → 1171.

version changed

Version changed: v0.87.10 → v0.87.11.

stars changed

Stars changed: 1152 → 1161.

version changed

Version changed: v0.87.8 → v0.87.10.

stars changed

Source-observed stars changed: 1147 → 1152. This reports the retained observation delta and does not infer why the upstream change occurred.

version changed

Source-observed version changed: v0.87.7 → v0.87.8. Associated release timestamp: 2026-07-31T16:30:23Z → 2026-08-01T06:44:07Z. This reports the retained observation delta and does not infer why the upstream change occurred.

stars changed

Stars changed: 1116 → 1124.

version changed

Version changed: v0.87.1 → v0.87.4.

version changed

Version changed: v0.81.2 → v0.87.1.

stars changed

Stars changed: 1029 → 1116.

stars changed

Source-observed stars changed: 1028 → 1029. This reports the retained observation delta and does not infer why the upstream change occurred.

version changed

Source-observed version changed: v0.81.1 → v0.81.2. Associated release timestamp: 2026-07-17T02:08:02Z → 2026-07-17T11:18:36Z. This reports the retained observation delta and does not infer why the upstream change occurred.