Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for developers who want to recover old AI coding context, understand which projects and models consumed time and money, and stop losing useful session history inside rotating CLI logs.
Who should use it
Who should skip it
Consider sudomichael/agentgraphed lower priority if you already have a working solution in this category.
About this signal
sudomichael/agentgraphed is tracked by RepoRadar as a developer tool in the Observability section. It was first seen on 2026-06-27 and last updated on 2026-06-27. The current verdict is 'try now' with a Gold tier and easy setup difficulty. Across RepoRadar's eight signals, sudomichael/agentgraphed is strongest on workflow potential (9.4) and practical usefulness (9.0) 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 sudomichael/agentgraphed a composite score of 8.3 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 43.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 vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
It indexes local Claude Code and Codex logs, which can include prompts, file paths, and project context you would not normally centralize; Optional provider keys are stored plaintext in the local SQLite database per the README, so the workstation threat model matters; The optional leaderboard and classification features can send metadata or sampled prompts off-box, so leave them disabled until you review the privacy model.