cspapers.org
A search engine dedicated to CS conferences. It provides useful filters for conferences and year range.
Runssource: GitHubhomepageGoMITcommit 92397bd6e241
Go, MIT licensed. The project labels itself: computer science, conference, indexing, publication and search engine.
cspapers.org runs. An Argusic agent installed it in 11 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The cspapers.org install builds (vite build produces docs/, go build and go test ./... pass) and the Go API server on localhost:8000 answers real searches over a bleve index built from the repo's shipped data (e.g. bluetooth query returned 51 hits with correct titles/years/venues), while the pre-2018 backfill and dupcheck remain blocked by the missing data/cstitles dumps that the repository does not include.
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.
- The Semantic Scholar title dumps data/cstitles/batch-0..3 are not in the repository, so `make index` panics ('open data/cstitles/batch-3: no such file') after indexing crawled papers, and `npm run test:dupcheck` exits ENOENT on missing 'data/' dir8 minutes
- Go toolchain and Node >=20 not installed in container (no root, no apt)3 minutes
- npm install under Node 18 missed the optional native rolldown binding (@rolldown/binding-linux-x64-gnu missing), so vite build failed with 'Cannot find native binding'3 minutes
- index.html references /src/index.js, but the repo contains only src/index.jsx, so vite build failed with 'Failed to resolve /src/index.js'1 minute
- The API index build is incomplete: without data/cstitles the indexer dies mid-run, so db.cspapers.org covers only data present in the repo (2017-2026 crawled abstracts); no full index exists
- Install time
- 11 minutes
- Cold machine to finish
- 9 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- curl 'http://localhost:8000/?query=bluetooth&yearFrom=2019&yearTo=2025&venue=NDSS,Usenix,SP,CCS&orderBy=score&ascending=false&skip=0' returned HTTP 200 with JSON {"total":51,...} (real titles/years/venues); robots.txt 200; bad query 400; 'go test ./...' exit 0 (config TestConfig and wordforms TestWords passed); 'npm run build' exit 0, 22 modules transformed; vite dev server on 5173 served index.html with '/src/index.jsx' and compiled const.js with VITE_API_HOST http://localhost:8000; vite preview served built site 200
- Model tokens used
- 417,345
- Exact commit tested
- 92397bd6e241
- 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.
=== M docs/index.html D docs/static/index-CU38kyp9.js M index.html ?? docs/static/index-CwPadjja.js === docs/CNAME db.cspapers.org All done. Real verification completed against the live Go API on a real index built from the repo's… tokens used 417,345 All done. Real verification completed against the live Go API on a real index built from the repo's…
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 11 minutes.
- Recovered from all 5 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.
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)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/cspapers-org)Questions
- Does cspapers.org run?
- Yes. cspapers.org runs. Argusic installed and launched it on a clean machine in 11 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test cspapers.org?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 92397bd6e241. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test cspapers.org?
- The run that produced this verdict cost $0.09: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does cspapers.org take to install?
- 11 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 cspapers.org need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing cspapers.org?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for cspapers.org?
- 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.