Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for AI builders, agent platform engineers, and security/QA teams who need to see exactly what a coding agent sent to the model and what came back, because Claude-Tap captures the full request/response stream in a local viewer, which means regressions, prompt-injection probes, and silent model swaps become visible and reproducible rather than guesswork from logs.
Where this stands now
liaohch3/claude-tap ranks #546 of 3231 tracked Radar items by composite score (8.0 against a section median of 4.9). The section currently carries 2115 Bronze, 645 Gold, 471 Silver. Signal extremes versus the section: momentum at the 76th percentile; novelty at the 85th percentile.
Who should use it
Who should skip it
Skip liaohch3/claude-tap unless the captured evidence suggests it solves a problem you are actively working on.
About this signal
liaohch3/claude-tap is tracked by RepoRadar as a developer tool in the Radar section. First seen —; the source record was last checked on 2026-06-21. The current verdict is 'try now' with a Gold tier and easy setup difficulty. Across RepoRadar's eight signals, liaohch3/claude-tap is strongest on workflow potential (9.5) and practical usefulness (9.0) and weakest on maturity (6.5) — a profile worth weighing against your own priorities. 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 liaohch3/claude-tap record combines a 8.0/10 composite score with separate popularity (7.5), risk (low), and setup (easy) signals. See the scoring methodology for the current weights and evidence definitions.
Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
It records full API traffic from coding agents including prompts and tool calls, so keep the trace viewer local, redact any captured secrets before sharing traces, and do not run it on workloads that mix production credentials with dev traffic.