xiadown
🐣一款支持视频下载的资源库管理应用 A media library manager with video download support
Not yet verifiedsource: GitHubhomepageGoApache-2.0commit c8e33101987f
Go, Apache-2.0 licensed. The project labels itself: bilibili, douyin, kuaishou, lo fi, music player, rss, sniff and tiktok.
xiadown has not been verified yet.
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 50 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 most recent recorded attempt, which did not reach a verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- go-json-experiment/[email protected] fails to build: references json.SkipFunc and json.DiscardUnknownMembers not in std encoding/json5 minutes
- Go 1.25.12+ not found1 minute
- Bun not found1 minute
- Missing system dev libraries (glib-2.0, gtk4, webkitgtk-6.0, libsoup-3.0, gio-2.0)
- IPv6 loopback [::1] unavailable in container
- Missing frontend bindings (bindings/ empty) and Wails CLI
- Install time
- 22 minutes
- Cold machine to finish
- 47 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- How the result was proved
- 43 of 63 Go packages passed (go test). 1426/1435 frontend JS tests passed (bun test). Root binary build fails on embedded frontend/dist and Wails system deps.
- Model tokens used
- 319,266
- Exact commit tested
- c8e33101987f
- 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.
7. **Missing `frontend/dist`** — prevents the main binary from compiling (`embed all:frontend/dist`… tokens used 319,266 Now I have a complete picture. Here's the final summary. **Errors encountered:** 1. **Go not installed** — downloaded `go1.27.2.linux-amd64.tar.gz`, installed to `/tmp/go-copy`, ad… 2. **Bun not installed** — `bun.sh/install` failed (no unzip), so downloaded bun binary from GitHub… 3. **`go-json-experiment/[email protected]` build failure** — the transitive dependency fr… 4. **Missing GTK4/WebKit2GTK system libraries** — required by Wails for the desktop app. `pkg-confi… 5. **`internal/infrastructure/libraryserver` test failures** — 4 tests fail because IPv6 loopback `… 6. **Missing frontend bindings** — `bindings/` directory is empty; the `wails3 generate bindings` c… 7. **Missing `frontend/dist`** — prevents the main binary from compiling (`embed all:frontend/dist`…
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.
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 | 1/3 | Did not run | 50.00 | 0.32 |
Topics (from GitHub)
bilibilidouyinkuaishoulo-fimusic-playerrsssnifftiktokvideo-downloadwailswails3xiaohongshuyoutube-music
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/xiadown)Questions
- Does xiadown run?
- xiadown has not been fully verified yet. No recorded run has produced a verdict yet.
- How did Argusic test xiadown?
- On a fresh, disposable machine, with every command recorded. One attempt is recorded, and the full method is on the methodology page.
- Where is the evidence for xiadown?
- 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.