Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
It is useful because AI coding costs often grow quietly until a team has no idea which tasks, prompts, or agents are responsible. Observability is a practical control surface, not a vanity metric.
Who should use it
Who should skip it
Move on from getagentseal/codeburn if the licensing terms, language support, or platform requirements do not fit your project.
About this signal
getagentseal/codeburn is tracked by RepoRadar as a developer tool in the Developer Productivity section. First seen 2026-06-18; the source record was last checked on 2026-06-18. The current verdict is 'try now' with a Gold tier and easy setup difficulty. The standout signals for getagentseal/codeburn 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 getagentseal/codeburn record combines a 8.5/10 composite score with separate popularity (92.0), risk (conditional), and setup (easy) signals. See the scoring methodology for the current weights and evidence definitions.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
Usage dashboards can surface prompt history or metadata from local coding sessions, so avoid sharing screenshots or exports from sensitive workspaces without review.