Does QZoneExport run?

Yes. QZoneExport runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 2 errors on the way, and recorded the session.

How did Argusic test QZoneExport?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit 7e0218fab293. One attempt is recorded, and the full method is on the methodology page.

What did it cost to test QZoneExport?

The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does QZoneExport 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 QZoneExport need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing QZoneExport?

2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.

Where is the evidence for QZoneExport?

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.

QZoneExport

QQ空间导出助手，用于备份QQ空间的说说、日志、私密日记、相册、视频、留言板、QQ好友、收藏夹、分享、最近访客为文件，便于迁移与保存

Runssource: GitHub homepageTypeScriptApache-2.0commit 7e0218fab293

TypeScript, Apache-2.0 licensed. The project labels itself: backup, chrome, chrome extension, chromium, crx, export, qq and qqzone.

QZoneExport runs. An Argusic agent installed it in 1 minute and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

npm install and all npm scripts (test, build, build:firefox, compile, build:viewer, dev:viewer) work with Node.js v22.14.0 and TZ=Asia/Shanghai. The 506-unit test suite passes. Both Chrome and Firefox browser extension builds (Manifest V3) complete successfully. The offline viewer builds and serves correctly.
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.07 (measured)
recorded runs: 1
last tested: 2026-10-05
stars: 1,876
forks: 207
open issues: 6
watchers: 1
size: 10 MB
created: 2019-03-10
last push: 2026-10-01

Subject data from GitHub, linked at the top of this page, refreshed 2026-10-04. 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 QZoneExport, 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.

System Node.js v18.19.1 does not meet project requirement of Node.js >=22. npm install failed with syntax errors in wxt (node:util parseEnv).0.5 minutes
2 of 506 tests failed due to timezone mismatch: tests expected China Standard Time (UTC+8) but container runs UTC.0.5 minutes

Install time: 1 minutes
Cold machine to finish: 9 minutes
Errors hit and fixed: 2 hit, 2 fixed with no human help
How the result was proved: TZ=Asia/Shanghai PATH=/tmp/node-v22.14.0-linux-x64/bin:$PATH npm test -> 41 files, 506 passed, 0 failed; npm run build && npm run build:firefox -> exit 0, manifests at .output/QZoneExport-{chrome,firefox}-mv3; viewer vite dev server -> curl http://localhost:5173/ returned 200 with expected HTML
Model tokens used: 39,800
Exact commit tested: 7e0218fab293
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.

 succeeded in 48680ms:
---COMPILE OK---
✔ Finished in 12.6 s
---BUILD OK---
 Test Files  41 passed (41)
      Tests  506 passed (506)
   Start at  21:24:44
   Duration  19.42s (transform 3.18s, setup 0ms, import 6.13s, tests 34.20s, environment 6.56s)
All verified. Here's the final result:
tokens used
39,800
All verified. Here's the final result:

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, faster than the median of the 15 comparable projects Argusic has measured.
Recovered from all 2 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 Apache-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.

Of the 16 backup projects Argusic has installed and timed, QZoneExport was the 2nd fastest to reach a running state, and 12 of 16 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.
A quick evaluation: it was running 1 minutes after the clone.

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	Runs	100.00	0.07	2026-10-05 13:25 UTC

Topics (from GitHub)

backup chrome chrome-extension chromium crx export qq qqzone qzone qzone-spider spider

Embed the badge

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

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

Questions

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