Castafiore
🎶 Castafiore is a music player that support Navidrome and Subsonic API.
Could not verifysource: GitHubhomepageJavaScriptUnlicensecommit 40c3cc60a309
JavaScript, Unlicense licensed. The project labels itself: android, apk, ios, music client, music player, navidrome, navidrome client and pwa.
Argusic could not get Castafiore running. An Argusic agent installed it in 1.5 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
The Castafiore Subsonic music player PWA builds and serves correctly via the web export pipeline: npm install completes, expo export -p web produces a valid dist/ with index.html, a 1.3 MB JS bundle, service worker, and assets all returning HTTP 200.
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 80 of 100 (the mean of this project's run scores).
At a glance
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
- 2 minutes
- Cold machine to finish
- 7 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- node.js http server on port 8085 served the built dist/ files: all 7 endpoints (/, index.html, favicon.ico, manifest.json, JS bundle, serviceWorker.js, workbox.js) returned HTTP 200. The 1.3 MB JS bundle is syntactically valid JS containing React components (Castafiore, Navigation, registerRootComponent). HTML includes all required PWA metadata (title, viewport, manifest link, DOCTYPE).
- Model tokens used
- 37,739
- Exact commit tested
- 40c3cc60a309
- 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
- Whether it works at all
- this run verified nothing, so this page makes no claim either way
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
-rw-rw-r-- 1 runner runner 4600 Sep 10 06:02 serviceWorker.js -rw-rw-r-- 1 runner runner 8479 Sep 10 06:02 serviceWorker.js.map -rw-rw-r-- 1 runner runner 21966 Sep 10 06:02 workbox-e3b5a6c9.js -rw-rw-r-- 1 runner runner 206871 Sep 10 06:02 workbox-e3b5a6c9.js.map === package.json scripts check === Scripts: export:android, export:google, export:dev, android, web, export:web, eslint, postinstall === npm install verification === /work/repo/node_modules/.package-lock.json node_modules present 2026-09-10T06:03:36.681532Z ERROR codex_core::session: failed to record rollout items: thread 01a08… tokens used 37,739
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
- Installed in 1.5 minutes, faster than the median of the 7 comparable projects Argusic has measured.
- Nothing broke on the way: zero errors between clone and running.
- Licensed Unlicense, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- An agent with no time limit did not get it running.
Of the 8 android projects Argusic has installed and timed, Castafiore was the 2nd fastest to reach a running state, and 7 of 8 reached one at all.
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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Unverified | 80.00 | 0.03 | |
| Argusic Runner | 1/3 | Unverified | 80.00 | 0.02 |
Topics (from GitHub)
androidapkiosmusic-clientmusic-playernavidromenavidrome-clientpwareact-nativereact-native-track-playersubsonicsubsonic-clientwindows
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/castafiore)Questions
- Does Castafiore run?
- Argusic could not verify that Castafiore runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test Castafiore?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 40c3cc60a309. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test Castafiore?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does Castafiore take to install?
- 1.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 Castafiore need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Castafiore?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does Castafiore compare with the alternatives?
- Of the 8 android projects Argusic has installed and timed, Castafiore was the 2nd fastest to reach a running state, and 7 of 8 reached one at all.
- Where is the evidence for Castafiore?
- 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.