limeplay

Modern UI Library for Video Players in React. @shaka-project for player engine and @shadcn-ui for installation. Beautifully designed & accessible components, packed with hooks.

Runssource: GitHubhomepageTypeScriptMITcommit eef715868500

TypeScript, MIT licensed. The project labels itself: dash, drm, headless, hls, library, modern, player and reactjs.

limeplay runs. An Argusic agent installed it in 0.3 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Limeplay installs, builds, populates a functional shadcn registry with 52 validated items, serves documentation and player blocks over HTTP, and its integration test successfully installs all blocks into freshly scaffolded Next.js and TanStack Start apps, all without leaving the container.

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.04 (measured)
recorded runs
1
last tested
stars
291
forks
19
open issues
1
watchers
1
size
20 MB
created
last push

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.

Time lost to each failure while testing limeplay, 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.

  • Container has Node 18 (project requires 23+) and no Bun (project requires bun 1.2.19)0.3 minutes
  • Registry build: shadcn child process used system Node 18, which lacks global File() type needed by undici v70.1 minutes
  • Registry install integration test: script calls 'bunx' but zip-only Bun install had no bunx shim0 minutes
Install time
under a minute
Cold machine to finish
8 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
bun run test:registry-install exited 0: 4/4 apps (nextjs + tanstack-start × radix + base) scaffolded, blocks installed from local registry server, and all built successfully. Also curl / and /api/health.json and /blocks/video-player and /r/registry.json and /docs/quick-start all returned 200. Production 'bun run build' generated 135 static pages.
Model tokens used
105,518
Exact commit tested
eef715868500
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

The end of the recording

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

 GET / 200 in 141ms (next.js: 12ms, application-code: 129ms)
(node:7036) ExperimentalWarning: Support for loading ES Module in require() is an experimental feat…
(Use `node --trace-warnings ...` to show where the warning was created)
UserJot client functions cannot be used on the server.
 GET /blocks/video-player 200 in 4.2s (next.js: 16ms, generate-params: 30ms, application-code: 4.2s)
\u0003[MDX] closing dev server
All real endpoints verified, registry install test 4/4 passed, production build succeeded. Now asse…
Here's the summary of everything done and observed:
tokens used
105,518
All real endpoints verified, registry install test 4/4 passed, production build succeeded. Now asse…
Here's the summary of everything done and observed:

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 0.3 minutes.
  • Recovered from all 3 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 MIT, as reported by its host.

What did not, or is not known

  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

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 0.3 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 byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.04

Topics (from GitHub)

dashdrmheadlesshlslibrarymodernplayerreactjsshadcnshadcn-uishaka-playerstreaminguivideo-player

Embed the badge

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

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

Questions

Does limeplay run?
Yes. limeplay runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test limeplay?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit eef715868500. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test limeplay?
The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does limeplay take to install?
0.3 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 limeplay need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing limeplay?
3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for limeplay?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion