clappr
An extensible, plugin-oriented, HTML5-first media player for the web
Runssource: GitHubhomepageJavaScriptBSD-3-Clausecommit 621ac457d623
JavaScript, BSD-3-Clause licensed. The project labels itself: clappr, dash, hls, html5 audio, html5 video, html5 video player, javascript and mp4.
clappr runs. An Argusic agent installed it in 4 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Clappr monorepo installs, builds (dev + minified dist), passes all 439 + 20 tests, and serves the player dev site at HTTP 200 on localhost:8080.
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
Subject data from GitHub, linked at the top of this page, refreshed . 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.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Node.js v18.19.1 but project requires >=24 (engines field)1 minute
- Yarn not installed in container1 minute
- npm lacked permission to write to /usr/local/lib/node_modules1 minute
- @babel/[email protected] engine check failed against node 24.0.0 (expected ^22.18.0 or >=24.11.0)1 minute
- Install time
- 4 minutes
- Cold machine to finish
- 11 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- yarn install exited 0; yarn test: 9/9 projects passed, 439 unit tests + 20 root tests all passed; yarn build:dist: 8/8 packages built; yarn dev: vite served HTTP 200 on localhost:8080
- Model tokens used
- 70,030
- Exact commit tested
- 621ac457d623
- Container image
- sha256:cdd920bce783
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.
- 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
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 2, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
Run duration: 3m 19s
Critical path: 3m 19s (1 task)
Recoverable time: <1ms
Recommendations:
- Speed up or split the longest tasks on the critical path:
@clappr/player:start 3m 19s
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Here is my final report.
tokens used
70,030
Here is my final report.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 4 minutes.
- Recovered from all 4 errors 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 BSD-3-Clause, as reported by its host.
- Measured 2 times, so the result is not a one-off.
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 4 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
Topics (from GitHub)
clapprdashhlshtml5-audiohtml5-videohtml5-video-playerjavascriptmp4playervideovideo-player
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/clappr)Questions
- Does clappr run?
- Yes. clappr runs. Argusic installed and launched it on a clean machine in 4 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test clappr?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 621ac457d623. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test clappr?
- The run that produced this verdict cost $0.11: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does clappr take to install?
- 4 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 clappr need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing clappr?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for clappr?
- 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.