ShiguReader

硬核宅宅资源管理器 Hardcore Otaku File Explorer

Runssource: GitHubJavaScriptMITcommit 480ef403493a

JavaScript, MIT licensed. The project labels itself: comics reader, doujin, doujin manager, full stack, ipad, manga, mobile web and music player application.

ShiguReader runs. An Argusic agent installed it in 2 minutes and hit 3 errors on a clean machine with no GPU, and the whole session was recorded.

ShiguReader backend starts, listens on port 3456+, serves the React frontend at HTTP 200, and responds to /api/folder/list_dir and /api/search/search_file with correct JSON structures. Frontend builds via webpack. All test suites execute; pre-existing failures are platform-specific (Windows path tests on Linux) and ESM-vs-CJS test harness mismatches.

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

At a glance

verdict
Runs
Argusic Score
86.7 / 100
cost of the verifying run
$0.02 (measured)
recorded runs
1
last tested
stars
418
forks
45
open issues
11
watchers
2
size
71 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.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • packages/backend/pathUtil.test.js: 10 tests fail on Linux — tests use Windows path conventions (C:\..., Y:\...)
  • packages/frontend/sender.test.js: 4 tests fail — ESM import in Sender.js not transpiled for CJS mocha runner
  • packages/name-parser: mocha missing from devDependencies
Install time
2 minutes
Cold machine to finish
4 minutes
Errors hit and fixed
3 hit, 1 fixed with no human help
How the result was proved
npm test backend: 30/40 pass; npm test frontend: 52/56 pass; npm test name-parser: 30/30 pass; curl localhost:3458 returned HTTP 200 serving React app; POST /api/folder/list_dir and /api/search/search_file returned correct JSON
Model tokens used
344,157
Exact commit tested
480ef403493a
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.

**Server verification:** Backend starts, listens, and serves:
- `GET /` returned HTTP **200** with the React HTML shell
- `POST /api/folder/list_dir` → valid JSON with `path`, `dirs`, `fileInfos`, `mode: "lack_info_mode…
- `POST /api/search/search_file` → valid JSON with `tag`, `author`, `fileInfos` fields
- Non-existent paths return `{"failed":true,"reason":"NOT FOUND"}`
**Test results:**
- `packages/backend`: **30 passing, 10 failing** (all 10 are pre-existing failures in `pathUtil.tes…
- `packages/frontend`: **52 passing, 4 failing** (all 4 are pre-existing — `sender.test.js` uses ES…
- `packages/name-parser`: **30 passing, 0 failing** (all pass after installing mocha)
**Errors found & fixed:**
- Name-parser had `mocha` in its `scripts.test` but missing from `devDependencies` — fixed by insta…
- The 10 + 4 pre-existing test failures are platform/test-environment mismatches, not code regressi…

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 2 minutes.
  • 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

  • Hit 3 errors during setup, 2 of which were not solved.
  • 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 2 minutes after the clone.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs86.670.02

Topics (from GitHub)

comics-readerdoujindoujin-managerfull-stackipadmangamobile-webmusic-player-applicationreactvideo-playervideo-player-applicationzip

Embed the badge

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

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

Questions

Does ShiguReader run?
Yes. ShiguReader runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test ShiguReader?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 480ef403493a. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test ShiguReader?
The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does ShiguReader take to install?
2 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 ShiguReader need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing ShiguReader?
3 things broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for ShiguReader?
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