Weibo-archiver
将微博导出备份的油猴脚本,为号被完全夹没前未雨绸缪 😭
Could not verifysource: GitHubhomepageTypeScriptApache-2.0commit 2416eafa798d
TypeScript, Apache-2.0 licensed. The project labels itself: archiver, backup, tampermonkey, violentmonkey, vue and weibo.
Argusic could not get Weibo-archiver running. An Argusic agent installed it in 6 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
CLI builds and shows help/error messages, Web app builds and serves on port 3336 with HTTP 200, Go server builds and serves on port 3000 with HTTP 200, Monkey script builds to weibo-archiver.user.js
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.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Node.js v18 too old, project requires >= 20.9.02 minutes
- pnpm 11.1.2 requires Node >= v22.13 but Node v20.18.3 was used after first upgrade2 minutes
- pnpm not installed, npm install -g failed due to EACCES on /usr/local/lib1 minute
- rm -rf rejected by sandbox; cannot delete node_modules directly1 minute
- Install time
- 6 minutes
- Cold machine to finish
- 10 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- node dist/weibo-archiver.mjs --help printed all 14 options correctly; curl to vite preview on port 3336 returned HTTP 200; curl to Go server on port 3000 returned HTTP 200
- Model tokens used
- 259,717
- Exact commit tested
- 2416eafa798d
- 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.
All projects build and run. Here's my findings summary: **Errors encountered:** 1. **Node.js v18 too old** — project requires >= 20.9.0. Fixed by downloading Node 22.14.0 and usin… 2. **pnpm not installed** — installed via `npm install -g pnpm` with custom `--prefix` (no root acc… 3. **pnpm 11.1.2 requires Node >= 22.13** — had to upgrade from v20.18.3 to v22.14.0. 4. **rm command rejected** — used Node.js `fs.rmSync` instead to clean `node_modules`. **Verification:** - CLI tool: `node ./dist/weibo-archiver.mjs --help` prints all 14 options correctly; `--uid=123` re… - Web app: `vite preview` on port 3336 → `curl` returned HTTP 200. - Go server: `weibo-archiver-server --server` on port 3000 → `curl` returned HTTP 200. - Monkey script: built to `dist/weibo-archiver.user.js` (233 kB). - No project test suites exist (vitest workspace config only sets up Storybook/test-addon, no actua…
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 6 minutes.
- Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed Apache-2.0, 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.
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)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/weibo-archiver)Questions
- Does Weibo-archiver run?
- Argusic could not verify that Weibo-archiver runs. Argusic installed and launched it on a clean machine in 6 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test Weibo-archiver?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 2416eafa798d. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test Weibo-archiver?
- 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 Weibo-archiver take to install?
- 6 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 Weibo-archiver need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Weibo-archiver?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for Weibo-archiver?
- 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.