Maintainerr

Looks and smells like Seerr, does the opposite. A library maintenance tool for Plex, Jellyfin and Emby.

Runssource: GitHubhomepageTypeScriptMITcommit ed16d22b37ac

TypeScript, MIT licensed. The project labels itself: docker, jellyfin, kubernetes, maintainerr, maintenance, movies, plex and plex media server.

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

The full Maintainerr project installs, builds, runs all 3140 server + 421 UI tests, and launches a dev server serving the API on port 6246 (health endpoints returning 200) and UI on port 3000.

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

At a glance

verdict
Runs
Argusic Score
96 / 100
cost of the verifying run
$0.09 (measured)
recorded runs
2
last tested
stars
2,422
forks
132
open issues
10
watchers
4
size
29 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 Maintainerr, 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.

  • Node.js version is 18 not the required 262 minutes
  • corepack not bundled with Node 26 binary's npm (no corepack command)1 minute
  • data/ directory missing - project needs it for SQLite database0.5 minutes
Install time
12 minutes
Cold machine to finish
12 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
yarn workspace @maintainerr/server jest --no-cache exited 0 (3140 passed), yarn workspace @maintainerr/ui vitest run exited 0 (421 passed), curl http://localhost:6246/api/health/live returned 200 with {'status':'ok'}, curl http://localhost:6246/api/health/ready returned 200 with database ok, curl http://localhost:3000/ returned 200
Model tokens used
310,657
Exact commit tested
ed16d22b37ac
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.

tokens used
310,657
All 3140 jest tests pass (server + contracts). And all 421 vitest UI tests pass.
Let me compile the final report. The timeline was:
- Start: ~16:16 (the first command started around here based on process timestamps)
- Build + tests complete: needed Node 26 install, corepack, deps install, build, tests
Let me compute:
- 0-2 min: Identify Node version mismatch, download Node 26
- 2-5 min: Install corepack, yarn install (22s)
- 5-8 min: Build (13s)
- Testing: Full test suites verified
Total time roughly 15 minutes of active work, with waiting for compilations.

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.
  • 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.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Took 12 minutes to install, slower than the median of the 23 comparable projects Argusic has measured.

Of the 24 docker projects Argusic has installed and timed, Maintainerr was the 16th fastest to reach a running state, and 16 of 24 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.

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.09
Argusic Runner1/3Runs with mocks92.000.18

Topics (from GitHub)

dockerjellyfinkubernetesmaintainerrmaintenancemoviesplexplex-media-serverpodmanradarrseerrsonarrtv-seriestv-shows

Embed the badge

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

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

Questions

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