Yes. jscpd runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 1 error on the way, and recorded the session.

How did Argusic test jscpd?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit 379057697f71. 2 attempts are recorded, and the full method is on the methodology page.

What did it cost to test jscpd?

The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does jscpd take to install?

2.5 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.

Does jscpd need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing jscpd?

1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.

Where is the evidence for jscpd?

All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

jscpd

Copy/paste detector for source code. 220+ languages, Rust engine, SARIF/HTML/badge reporters, GitHub Action, MCP server for AI agents.

Runssource: GitHub homepageRustMITcommit 379057697f71

Rust, MIT licensed. The project labels itself: ai, cli, clones detection, code duplication, code quality, coding agents, copy paste and copy paste detection.

jscpd runs. An Argusic agent installed it in 2.5 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

jscpd v5.1.2 installed and running via prebuilt binary: detects clones across 224 formats, all 15 reporters functional, MCP server operational, threshold/exit codes correct
What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).

At a glance

verdict: Runs
Argusic Score: 100 / 100
cost of the verifying run: $0.07 (measured)
recorded runs: 2
last tested: 2026-09-03
stars: 6,258
forks: 265
open issues: 40
watchers: 28
size: 15 MB
created: 2013-05-29
last push: 2026-09-22

Subject data from GitHub, linked at the top of this page, refreshed 2026-09-23. Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing jscpd, drawn from the recorded run — Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

Rust source build fails: no C compiler (gcc/cc) or system linker available in container; cannot install build-essential without root8 minutes

Install time: 3 minutes
Cold machine to finish: 20 minutes
Errors hit and fixed: 1 hit, 1 fixed with no human help
Model tokens used: 253,570
Exact commit tested: 379057697f71
Container image: sha256:4c3d41857be3

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

How the result was proved: runs before 2026-09-07 did not record the command used to check the result
Peak GPU memory: this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run: each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

5. Verified all reporters (console, json, html, csv, xml, markdown, ai, threshold)
6. Verified blame, summary, MCP server, threshold exit code, cross-format detection
7. Confirmed both `jscpd` and `cpd` binaries work identically
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 2…
 succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 2.5, "errors": [{"msg": "R…
exec
/bin/sh -lc 'echo "ARGUSIC_RESULT:$(echo '"'{\"install_succeeded\": true, \"launch_succeeded\": tru…
 succeeded in 0ms:
tokens used
253,570

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

Reached a running state on a clean machine, with the session recorded.
Installed in 2.5 minutes, faster than the median of the 36 comparable projects Argusic has measured.
Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
Ran without a GPU, so it does not need one to start.
Licensed MIT, as reported by its host.
Measured 2 times, so the result is not a one-off.

Of the 37 ai projects Argusic has installed and timed, jscpd was the 9th fastest to reach a running state, and 30 of 37 reached one at all.

What it is a reasonable choice for

Trying it on a laptop or a small server: it reached a running state without a GPU.
A quick evaluation: it was running 2.5 minutes after the clone.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested by	attempt	outcome	score	cost USD	when
Argusic Runner	2/3	Runs	100.00	0.07	2026-09-03 17:07 UTC
Argusic Runner	1/3	Ran out of time	0.00	0.16	2026-09-03 14:36 UTC

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/jscpd.svg)](https://argusic.com/subject/jscpd)

Questions

Does jscpd run?: Yes. jscpd runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 1 error on the way, and recorded the session.
How did Argusic test jscpd?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 379057697f71. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test jscpd?: The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does jscpd take to install?: 2.5 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does jscpd need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing jscpd?: 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does jscpd compare with the alternatives?: Of the 37 ai projects Argusic has installed and timed, jscpd was the 9th fastest to reach a running state, and 30 of 37 reached one at all.
Where is the evidence for jscpd?: All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.