NASSAV

nas全自动小姐姐下载器。已实现的数据源有missav、jable(持续增加中),可自定义拓展下载器

Runs with mockssource: GitHubPythonMITcommit 0c5ff7fe11d7

Python, MIT licensed. The project labels itself: jable, jav, jellyfin, missav and nfo.

NASSAV runs, with stand-ins for the services it depends on. An Argusic agent installed it in 18 minutes and hit 7 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Python download pipeline runs end-to-end against local mocks producing decodable mp4 files, NFO, metadata JSON, and SQLite dedup; the Go backend serves gallery JSON/image/video endpoints with 200s; the frontend builds; all installs (Python deps, npm, local Go toolchain) succeeded.

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

At a glance

verdict
Runs with mocks
Argusic Score
56 / 100
cost of the verifying run
$0.28 (measured)
recorded runs
2
last tested
stars
482
forks
91
open issues
4
watchers
6
size
70 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.

Time lost to each failure while testing NASSAV, 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.

  • curl_cffi ignores SSL_CERT_FILE and no /etc/hosts write access, so real hostnames (memojav.com, www.javbus.com) could not be pointed at the local mock25 minutes
  • scraper cover image fetch returned HTTP 405 Method Not Allowed through the proxy10 minutes
  • m3u8-Downloader-Go download failed against the mock: tls: certificate signed by unknown authority with proxy, then 404 without proxy8 minutes
  • go binary not installed and no root to apt-install it (README requires Go 1.22.6)3 minutes
  • mock's Memo get_video_info returned a raw URL but MemoDownloader.parseHTML expects percent-encoded https%3A%2F%2F URL3 minutes
  • relative fanart sample URLs in the JavBus mock page failed with 'URL rejected: No host part' (app does not absolutize relative URLs)2 minutes
Install time
18 minutes
Cold machine to finish
17 minutes
Errors hit and fixed
7 hit, 7 fixed with no human help
How the result was proved
main.py ABP-490 exited 0 with save/ABP-490/ABP-490.mp4 ffmpeg -v error -i ... -f null - clean (duration=16.0s via ffprobe); sqlite3 MissAV rows 2; curl /api/videos returned 200 [{"id":"ABP-490",...}]; curl /api/videos/ABP-490 returned 200 with videoFile; curl /file/ABP-490/ABP-490-poster.jpg returned 200 and decodes; curl /api/addvideo/ABP-490 returned 401; npm run build exited 0
Model tokens used
1,352,088
Exact commit tested
0c5ff7fe11d7
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
Behaviour against real services
this run was verified against stand-in services only

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

**What I verified (tier2_mock, always observed)**
- Full download path via a schema-accurate local mock (HTTPS `memojav.com` + `www.javbus.com` throu…
- Backend: `go build -o main.new` OK; server started on :31471, `/api/videos` → `200 [{"id":"ABP-49…
**Errors fixed**
- Go missing (no root) → local Go 1.22.6 toolchain; build passes.
- `curl_cffi` ignores `SSL_CERT_FILE` → mock uses `NASSAV_VERIFY` (CA path passed via `verify=`) pl…
- m3u8 downloader binary failed TLS/404 vs mock → `-s` (skipverify) added in `downloadM3u8`; also i…
- Scraper cover/sample URLs were plain HTTPS-port URLs that broke behind the proxy → mock returns a…
- Backend hardcoded `/vol2` (not writable, README said edit) → changed `basePath` to `/work/repo/ga…
**Caveats**
- System packages can’t be installed (no root); Go was fetched to home, the project’s bundled binar…
- Modified project files (tracked in `git status`): `backend/main.go`, `cfg/configs.json`, `src/dow…

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 18 minutes.
  • Recovered from all 7 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.

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 byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs with mocks92.000.28
Argusic Runner1/3Did not run20.000.09

Topics (from GitHub)

jablejavjellyfinmissavnfo

Embed the badge

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

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

Questions

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

Discussion