Item detail
github.com

kucherenko/jscpd

RepoRadar surfaced kucherenko/jscpd — a developer tool — into the Radar section, where it sits at Silver tier with a 'try now' verdict. Its strongest signal is workflow potential, scored 9.0 out of 10.

Score7.9
Popularity6.7
Risklow
TierSilver
Score breakdown
Usefulness8.0
Novelty8.0
Momentum7.0
Maturity5.9
Open-source/build8.4
Evidence7.2
Workflow potential9.0
Setup ease8.8

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.

Who should use it

engineering leads who want a fast, self-hostable copy/paste detector that fits into CI code-review teams that want AI-friendly duplicate-code reports across many languages AI coding-agent builders who want a real MCP-server tool for flagging copy/paste hot spots refactor project owners who need a token-efficient duplicate-code report on a large repo

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.

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.

Evidence links
Closest alternatives / related signals
code-quality copy-paste ci mcp ai-coding rust open-source
Verification record

What RepoRadar actually verified

Tested in a bounded workflow

Bounded representative workflow retained by RepoRadar verification harness. Last checked 2026-07-13T10:41:51.627315Z.

passed · cohort-20260712-jscpd-duplicate-detection-workflow

Tester
RepoRadar automated local verification harness
Started
2026-07-13T10:41:50.089835Z
Completed
2026-07-13T10:41:51.627315Z
Environment
Windows 10 AMD64; Python 3.11.9; credential-stripped child environment; disposable home/cache
Install/setup time
1 minute(s)
Evidence scope
Bounded representative workflow
Cleanup
Per-check temporary home and work directory removed. Shared cohort package cache removed.
Actions exercised
  • Created a disposable home, work directory, and isolated package cache with credential-like environment variables excluded.
  • Created 2 synthetic fixture file(s) inside the disposable work directory; retained hashes prove the exact inputs.
  • Created two JavaScript modules with an intentionally duplicated incident-normalization block.
  • Ran jscpd with explicit line/token thresholds and JSON reporting, then validated both file names and the one-clone statistic in the report.
  • Executed bounded check: Scan two synthetic JavaScript modules and retain a structured duplicate-code report.
  • Captured the complete sanitized stdout, stderr, exit status, artifact checks, and 1.54-second wall time.
Observed results
  • Command exited 0 after 1.54 seconds.
  • jscpd detected the shared normalization block and emitted a machine-readable report naming both fixture files.
  • Validated report/jscpd-report.json: 4 required marker(s) present and 0 excluded marker(s) absent; size and SHA-256 are retained.
Observed strengths
  • The CLI turns cross-file clone detection into a deterministic JSON artifact suitable for a CI quality gate.
Friction
  • Detection sensitivity depends on explicit line and token thresholds; small changes to the fixture or parser can change clone boundaries.
Limitations
  • The small exact-duplicate fixture validates tokenization, block detection, and JSON reporting, not language breadth, incremental scans, CI thresholds, or large-repository performance.
  • This credential-free disposable workflow does not establish production scale, model quality, reliability under sustained use, or team adoption.

Pricing assessment: The local open-source jscpd CLI scanned disposable source with no hosted analysis or paid plan.

Privacy assessment: Only synthetic JavaScript files were read locally; npm was contacted for package resolution, but source content was not uploaded.

Open retained test log →

Verification sources

Longitudinal intelligence

How this decision record is moving

Raw history JSON →

44 dated snapshots retained from 2026-06-21 through 2026-08-13; see the snapshot index for explicit coverage gaps. Stars, version, release, pricing, integration, risk, maintenance, verdict, score, and momentum fields remain explicit even when a source has not reported them. Repository momentum is a normalized 0–10 RepoRadar signal; GitHub stars appear only where the popularity monitor retained exact timestamped observations.

RepoRadar score7.9 current · +0.0 net
Repository momentum9.3 current · +2.3 net
GitHub stars (observed)5,999 current · +126 net
GitHub stars5,999 exact observation
Versionv4.3.0
Last release2026-08-13T16:09:20Z
Maintenanceactive
Current risklow
Current verdicttry now
Pricing baselineNo structured commercial pricing baseline
Pricing checkedNot applicable or not recorded
Pricing freshnessNo dated commercial pricing review
Integrations baselineModel Context Protocol

Recent dated points

DateScoreMomentumStarsRiskVerdictMaintenance
2026-08-137.99.35,999lowtry nowactive
2026-08-127.99.35,990lowtry nowactive
2026-08-117.99.35,985lowtry nowactive
2026-08-107.99.05,982lowtry nowactive
2026-08-097.99.35,982lowtry nowactive
2026-08-087.99.35,980lowtry nowactive
2026-08-077.99.35,965lowtry nowactive
2026-08-067.97.0Not recordedlowtry nownot recorded
2026-08-057.97.0Not recordedlowtry nownot recorded
2026-08-047.99.35,965lowtry nowactive
2026-08-037.99.35,965lowtry nowactive
2026-08-027.99.35,959lowtry nowactive

Why the record changed

version changed

Version changed: v5.0.14 → v4.3.0.

stars changed

Stars changed: 5990 → 5999.

stars changed

Stars changed: 5985 → 5990.

stars changed

Stars changed: 5982 → 5985.

stars changed

Stars changed: 5980 → 5982.

stars changed

Stars changed: 5965 → 5980.

stars changed

Stars changed: 5959 → 5965.

stars changed

Stars changed: 5957 → 5959.

stars changed

Source-observed stars changed: 5958 → 5957. This reports the retained observation delta and does not infer why the upstream change occurred.

stars changed

Stars changed: 5941 → 5946.

stars changed

Source-observed stars changed: 5940 → 5941. This reports the retained observation delta and does not infer why the upstream change occurred.

version changed

Version changed: v5.0.12 → v5.0.14.