jellyfin-ios

Jellyfin for iOS

Runssource: GitHubhomepageJavaScriptMPL-2.0commit 84bf59e1ebac

JavaScript, MPL-2.0 licensed. The project labels itself: expo, ios, jellyfin, media playback and react native.

jellyfin-ios runs. An Argusic agent installed it in 1 minute and hit no errors on a clean machine with no GPU, and the whole session was recorded.

npm install succeeded with 1734 packages, full test suite passes (38 suites, 143 tests, 22 snapshots, 0 failures).

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
626
forks
155
open issues
81
watchers
16
size
5 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.

Install time
1 minutes
Cold machine to finish
7 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
npx jest --no-watchAll exited 0, 38 suites 143 tests 22 snapshots all passed
Model tokens used
28,740
Exact commit tested
84bf59e1ebac
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 1, 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.

- The `postinstall` patch (`git apply patches/boost1760.patch`) ran without issue
**Test summary:**
- Ran the full Jest test suite twice
- 38 test suites passed, 143 tests passed, 22 snapshots passed
- No test failures at all
**Verified:**
```sh
npx jest --no-watchAll  # returns exit 0
Test Suites: 38 passed, 38 total
Tests:       143 passed, 143 total
Snapshots:   22 passed, 22 total
```

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 1 minute.
  • Nothing broke on the way: zero errors between clone and running.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MPL-2.0, 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 1 minutes after the clone.
  • Following its own README: the documented path worked with nothing to fix.

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)

expoiosjellyfinmedia-playbackreact-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-ios.svg)](https://argusic.com/subject/jellyfin-ios)

Questions

Does jellyfin-ios run?
Yes. jellyfin-ios runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test jellyfin-ios?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 84bf59e1ebac. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test jellyfin-ios?
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 jellyfin-ios take to install?
1 minute 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-ios need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing jellyfin-ios?
Nothing did, in the recorded run: zero errors between clone and running.
Where is the evidence for jellyfin-ios?
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