fluid-player

Fluid Player - an open source VAST compliant HTML5 video player

Runssource: GitHubhomepageJavaScriptMITcommit 026a61c8be3a

JavaScript, MIT licensed. The project labels itself: html5 player, html5 video, javascript, javascript library, video player and video streaming.

fluid-player runs. An Argusic agent installed it in 15 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

npm install exited 0, webpack build compiled successfully, Python HTTP dev server serves all pages with 200, and 7/8 e2e tests pass on Firefox including controls, ad interaction, and suggested videos

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 60 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
60 / 100
cost of the verifying run
$0.21 (measured)
recorded runs
2
last tested
stars
961
forks
423
open issues
43
watchers
221
size
52 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 fluid-player, 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.

  • External video URLs (commondatastorage.googleapis.com) returned HTTP 403, blocking video playback in tests8 minutes
  • Firefox autoplay policy blocked video playback after ad transitions during midRoll test5 minutes
  • webpack-dev-server crashed with EMFILE (too many open watched files)3 minutes
  • Playwright Firefox could not connect to dev server (NS_ERROR_CONNECTION_REFUSED) due to IPv6/IPv4 mismatch2 minutes
Install time
15 minutes
Cold machine to finish
32 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
npx playwright test exited with 7 passed, 1 failed (pre-existing midRoll ad transition issue in headless Firefox). The 7 passing tests: ad click navigation, ad skip blocking, impression URL tracking, play/pause toggle, cursor hiding on hover, skip animation icons, and suggested videos grid
Model tokens used
474,032
Exact commit tested
026a61c8be3a
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.

exec
/bin/sh -lc '# Kill any remaining background processes
kill %1 %2 %3 2>/dev/null; true' in /work/repo
 succeeded in 0ms:
7/8 e2e tests pass on Firefox. The single failure (`ads_linear.spec.ts:40` - pre/mid/postRoll flow)…
Here's the final result:
2026-10-11T20:32:21.710946Z ERROR codex_core::session: failed to record rollout items: thread 01a12…
2026-10-11T20:32:21.710996Z ERROR codex_core::session: failed to record rollout items: thread 01a12…
tokens used
474,032
7/8 e2e tests pass on Firefox. The single failure (`ads_linear.spec.ts:40` - pre/mid/postRoll flow)…
Here's the final result:

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 15 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 MIT, 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.

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 Runner2/3Runs100.000.21
Argusic Runner1/3Did not run20.000.87

Topics (from GitHub)

html5-playerhtml5-videojavascriptjavascript-libraryvideo-playervideo-streaming

Embed the badge

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

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

Questions

Does fluid-player run?
Yes. fluid-player runs. Argusic installed and launched it on a clean machine in 15 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test fluid-player?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 026a61c8be3a. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test fluid-player?
The run that produced this verdict cost $0.21: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does fluid-player take to install?
15 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 fluid-player need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing fluid-player?
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 fluid-player?
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.

Discussion