Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for developers and indie builders who want a simple way to see what their tools are actually spending without changing SDK code or sending telemetry to another SaaS.
Who should use it
Who should skip it
Pass on camelyello-88/llmstat if its scope or audience does not match what your team is building right now.
About this signal
camelyello-88/llmstat is tracked by RepoRadar as a cost proxy in the Model Infrastructure section. It was first seen on 2026-06-29 and last updated on 2026-06-29. The current verdict is 'try now' with a Silver tier and easy setup difficulty. camelyello-88/llmstat leads on workflow potential (8.9) and setup ease (8.8); its lowest signal is momentum (4.0), so factor that in before investing setup time. 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 camelyello-88/llmstat a composite score of 7.8 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 11.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
As a local proxy it sees full prompts, tool output, and usage metadata, so do not point sensitive production traffic at it before reviewing local logging and storage; Built-in pricing tables can drift from provider changes, so verify custom rates before using it for chargeback or budget enforcement.