jellyfin-audio-player

🎵 A gorgeous Jellyfin audio streaming app for iOS and Android

Runssource: GitHubhomepageTypeScriptMITcommit 13f25aca597b

TypeScript, MIT licensed. The project labels itself: android, ios, jellyfin, mobile app, music player and react native.

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

pnpm install succeeds, Jest test suite passes (1/1), TypeScript type-checks clean, ESLint passes (0 errors, 110 pre-existing warnings), and the React Native Metro dev server starts successfully with Node 22.

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.10 (measured)
recorded runs
1
last tested
stars
1,415
forks
64
open issues
120
watchers
12
size
26 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 jellyfin-audio-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.

  • Jest fails: Cannot use import statement outside a module on react-native/jest/setup.js caused by pnpm virtual store paths not matching transformIgnorePatterns3 minutes
  • Metro fails: configs.toReversed is not a function (Node 18 lacks Array.prototype.toReversed)3 minutes
  • pnpm not found in PATH after npm install -g1 minute
  • pnpm approve-builds requires interactive terminal1 minute
Install time
5 minutes
Cold machine to finish
9 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
pnpm test exited 0, 1/1 passed; npx tsc --noEmit exited 0; npx eslint exited 0 errors; Metro dev server started Dev server ready on Node 22
Model tokens used
81,575
Exact commit tested
13f25aca597b
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.

  pnpm install + perms: ~2 min
  approve-builds issue: ~1 min
  Jest pnpm compat fix: ~3 min
  Node22 install: ~3 min
  Verification runs: ~3 min
Total: ~12 min
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 5…
 succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 5, "errors": [{"msg": "pnp…
tokens used
81,575

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 5 minutes, faster than the median of the 18 comparable projects Argusic has measured.
  • 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.

What did not, or is not known

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

Of the 19 android projects Argusic has installed and timed, jellyfin-audio-player was the 9th fastest to reach a running state, and 14 of 19 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 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 byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.10

Topics (from GitHub)

androidiosjellyfinmobile-appmusic-playerreact-native

Embed the badge

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

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

Questions

Does jellyfin-audio-player run?
Yes. jellyfin-audio-player runs. Argusic installed and launched it on a clean machine in 5 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test jellyfin-audio-player?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 13f25aca597b. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test jellyfin-audio-player?
The run that produced this verdict cost $0.10: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does jellyfin-audio-player take to install?
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 jellyfin-audio-player need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing jellyfin-audio-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.
How does jellyfin-audio-player compare with the alternatives?
Of the 19 android projects Argusic has installed and timed, jellyfin-audio-player was the 9th fastest to reach a running state, and 14 of 19 reached one at all.
Where is the evidence for jellyfin-audio-player?
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