JMComic-Crawler-Python
Python API for JMComic | 提供Python API访问禁漫天堂，同时支持网页端和移动端 | 禁漫天堂GitHub Actions下载器🚀
Runssource: GitHubhomepagePythonMITcommit 2838d116de31
Python, MIT licensed. The project labels itself: 18comic, asyncio, crawler, downloader, github actions, jmcomic, pypi and python.
JMComic-Crawler-Python runs. An Argusic agent installed it in 8 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Package jmcomic 2.7.7 installed in a Python 3.12.3 venv with all dependencies; 238/240 tests pass including real network calls against JMComic API servers; CLI commands jmcomic and jmv produce correct help output
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
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.
- Missing option_test.yml (no option_test.yml in assets/option/, only option_test_api.yml and option_test_html.yml existed)1 minute
- test_sync_progress_is_rendered_before_download_finishes: assertIn('本子-JM123456', '') — rendered output empty at time of assertion, a timing race in rich console rendering
- test_plugin_uses_real_scheduler_without_stdout_or_image_io: assertIn('album.before', rendered) — 'album.before' not found in rendered rich output (only image.after/photo.after/album.after present), a rendering-order timing issue
- Install time
- 8 minutes
- Cold machine to finish
- 10 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- python -m unittest discover -s test_jmcomic -p 'test_*.py': 240 tests ran, 238 ok, 2 FAILED (pre-existing rich console rendering timing issues)
- Model tokens used
- 70,216
- Exact commit tested
- 2838d116de31
- 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.
- **Two pre-existing test failures** in `test_jm_download_progress`: both are rendering-timing asse… - **Real API tests**: Multiple tests (test_jm_client, test_jm_api, test_jm_async_client, test_jm_as… - **CLI entry points**: `jmcomic` and `jmv` installed and respond to `--help`. tokens used 70,216 All 240 tests executed across the full test suite. 238 passed, 2 pre-existing timing-related failur… ## Summary - **Install**: `pip install -e ".[plugins]"` in a fresh venv — all dependencies resolved, no errors. - **Missing config file**: `./assets/option/option_test.yml` didn't exist; the test harness expecte… - **Two pre-existing test failures** in `test_jm_download_progress`: both are rendering-timing asse… - **Real API tests**: Multiple tests (test_jm_client, test_jm_api, test_jm_async_client, test_jm_as… - **CLI entry points**: `jmcomic` and `jmv` installed and respond to `--help`.
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 8 minutes.
- Recovered from all 3 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 MIT, 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.
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 8 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
Topics (from GitHub)
18comicasynciocrawlerdownloadergithub-actionsjmcomicpypipythonreadthedocs
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/jmcomic-crawler-python)Questions
- Does JMComic-Crawler-Python run?
- Yes. JMComic-Crawler-Python runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test JMComic-Crawler-Python?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 2838d116de31. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test JMComic-Crawler-Python?
- The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does JMComic-Crawler-Python take to install?
- 8 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 JMComic-Crawler-Python need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing JMComic-Crawler-Python?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for JMComic-Crawler-Python?
- 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.