clip-js
online video editor built with nextjs, remotion and ffmpeg (web assembly port) for render.
Could not verifysource: GitHubhomepageTypeScriptMITcommit 48a4099942bd
TypeScript, MIT licensed. The project labels itself: canvas, editor, ffmpeg, nextjs, reactjs, remotion, remotion video and render.
Argusic could not get clip-js running. An Argusic agent installed it in 0.4 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
npm install and build succeed, the Next.js dev server starts and serves all static and dynamic pages with correct HTTP status codes.
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 80 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.
- Install time
- under a minute
- Cold machine to finish
- 3 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- curl http://localhost:3000/ returned 200 (21807 bytes), /about 200 (16319 bytes), /projects 200 (13780 bytes), /projects/abc123 200 (70987 bytes), /nonexistent 404 (13124 bytes)
- Model tokens used
- 26,943
- Exact commit tested
- 48a4099942bd
- 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
- Whether it works at all
- this run verified nothing, so this page makes no claim either way
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
## Verification results | Route | Status | Size | |---|---|---| | `/` | 200 | 21,807 bytes | | `/about` | 200 | 16,319 bytes | | `/projects` | 200 | 13,780 bytes | | `/projects/abc123` (dynamic) | 200 | 70,987 bytes | | `/_not_found` | 404 | 13,123 bytes | | `/nonexistent` | 404 | 13,124 bytes | No tests exist in the project (no test runner or spec files). No third-party API keys were needed —… ``` ```
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
- Installed in 0.4 minutes, faster than the median of the 8 comparable projects Argusic has measured.
- Nothing broke on the way: zero errors between clone and running.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- An agent with no time limit did not get it running.
Of the 9 canvas projects Argusic has installed and timed, clip-js was the 3rd fastest to reach a running state, and 6 of 9 reached one at all.
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 | Unverified | 80.00 | 0.03 | |
| Argusic Runner | 1/3 | Unverified | 80.00 | 0.05 |
Topics (from GitHub)
canvaseditorffmpegnextjsreactjsremotionremotion-videorendervideo-editingwebassembly
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/clip-js)Questions
- Does clip-js run?
- Argusic could not verify that clip-js runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test clip-js?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 48a4099942bd. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test clip-js?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does clip-js take to install?
- 0.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 clip-js need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing clip-js?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does clip-js compare with the alternatives?
- Of the 9 canvas projects Argusic has installed and timed, clip-js was the 3rd fastest to reach a running state, and 6 of 9 reached one at all.
- Where is the evidence for clip-js?
- 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.