Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for heavy Claude Code, Codex, Cursor, and Gemini CLI users who need a glanceable local read on burn rate and remaining quota instead of checking each tool separately.
Who should use it
Who should skip it
Pass on Nanako0129/TokenBar if its scope or audience does not match what your team is building right now.
About this signal
Nanako0129/TokenBar is tracked by RepoRadar as a usage monitor 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 easy setup difficulty. Across RepoRadar's eight signals, Nanako0129/TokenBar is strongest on workflow potential (9.7) and setup ease (8.8) and weakest on momentum (6.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 Nanako0129/TokenBar 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
It reads local coding-agent session and usage artifacts across multiple tools, so first use should stay on a trusted personal machine until you confirm exactly which files it parses; macOS-only utility today, so teams on mixed operating systems should treat it as a personal productivity tool rather than a shared standard.