Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for developers who are starting to compare or debug agent runs and need a lightweight local viewer before they stand up a full tracing stack.
Who should use it
Who should skip it
Move on from unixzii/agent-explorer if the licensing terms, language support, or platform requirements do not fit your project.
About this signal
unixzii/agent-explorer is tracked by RepoRadar as a agent observability in the Developer Tools section. It was first seen on 2026-06-30 and last updated on 2026-06-30. The current verdict is 'try now' with a Silver tier and easy setup difficulty. unixzii/agent-explorer leads on workflow potential (9.4) and setup ease (8.8); its lowest signal is momentum (5.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 unixzii/agent-explorer a composite score of 7.9 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 1.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 vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
Session logs can contain prompts, tool outputs, and sensitive file paths, so open only transcripts you are allowed to inspect and sanitize before sharing screenshots; The current parser coverage is intentionally narrow around Claude Code and Codex JSONL formats, so verify format compatibility before making it part of a broader team workflow.