Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for engineering leads, code-review teams, and AI coding-agent builders who want a self-hostable, AI-friendly copy/paste detector that works across hundreds of languages, integrates into CI, and gives their agents a real MCP tool for flagging duplicated code in pull requests and large refactors.
Where this stands now
kucherenko/jscpd ranks #644 of 2304 tracked Radar items by composite score (7.9 against a section median of 5.2). The section currently carries 1197 Bronze, 645 Gold, 462 Silver. RepoRadar has retained observations for this record since 2026-06-21 (98 days in the current window). Signal extremes versus the section: novelty at the 79th percentile.
Who should use it
Who should skip it
Skip kucherenko/jscpd if the source link, documentation, or setup requirements do not align with your current workflow or stack.
About this signal
kucherenko/jscpd is tracked by RepoRadar as a developer tool in the Radar section. First seen 2026-06-21; the source record was last checked on 2026-06-21. The current verdict is 'try now' with a Silver tier and easy setup difficulty. kucherenko/jscpd leads on workflow potential (9.0) and setup ease (8.8); its lowest signal is maturity (5.9), so factor that in before investing setup time. 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 kucherenko/jscpd record combines a 7.9/10 composite score with separate popularity (6.7), risk (low), and setup (easy) signals. See the scoring methodology for the current weights and evidence definitions.
Questions worth asking before you adopt this
Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
It scans source code and emits reports that may include code snippets, so confirm where reports get stored, who can read them, and what redaction is in place before running it against proprietary codebases.