gspread runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 4 minutes, hitting 2 errors on the way, and recorded the session.

How did Argusic test gspread?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit 7ca71eaa4658. 3 attempts are recorded, and the full method is on the methodology page.

What did it cost to test gspread?

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

How long does gspread take to install?

4 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 gspread need a GPU?

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

What goes wrong when installing gspread?

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 gspread?

All 3 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.

gspread

Google Sheets Python API

Runs with mockssource: GitHub homepagePythonMITcommit 7ca71eaa4658

Python, MIT licensed. The project labels itself: google sheets, google sheets api, google sheets api v4, gspread, spreadsheet and spreadsheets.

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

gspread 6.2.1 installs in a venv, its 166-test suite passes, and a local schema-correct TLS mock of the Sheets/Drive APIs returns 200 for a full read/write/create/append/clear workflow through the real gspread client.
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 92 of 100 (the mean of this project's run scores).

At a glance

verdict: Runs with mocks
Argusic Score: 92 / 100
cost of the verifying run: $1.01 (measured)
recorded runs: 3
last tested: 2026-09-23
stars: 7,513
forks: 981
open issues: 82
watchers: 154
size: 4 MB
created: 2011-12-02
last push: 2026-07-30

Subject data from GitHub, linked at the top of this page, refreshed 2026-11-07. 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 gspread, 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.

requests 2.34.2 installed in a new venv redirects googleapis hostname resolution in ways that blocked my first local mock approach (DNS rewrite + adapter rewrite variants hit refused port 443); resolved by patching socket.getaddrinfo in the harness and adding a per-mount URL port rewrite42 minutes
Local mock's values-endpoint range parser crashed on gspread's %27Sheet1%27!A1%3A1 and row/col-range forms (A1:1, A1:A), closing connections; fixed expand_labeled normalization and added majorDimension=COLUMNS transposition30 minutes

Install time: 4 minutes
Cold machine to finish: 48 minutes
Errors hit and fixed: 2 hit, 2 fixed with no human help
How the result was proved: pytest tests/ -q returned '166 passed in 1.68s'; .venv/bin/python -c 'import gspread; print(gspread.__version__)' printed 6.2.1; mock e2e (final_e2e.py) printed FINAL_E2E_OK plus open_by_key title 'Mock Financial Data' and get A1:B2 == [[a,b],[c,d]]; mock HTTP GET returned status 200
Model tokens used: 5,135,023
Exact commit tested: 7ca71eaa4658
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.

print('mock HTTP status:', r.status_code)
\"" in /work/repo
 succeeded in 853ms:
row_values(1): ['a', 'b', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '…
mock HTTP status: 200
Verification is complete and reproducible. Final result summary:
exec
/bin/sh -lc 'cd /work/repo && .venv/bin/python -m pytest tests/ -q 2>&1 | tail -1' in /work/repo
 succeeded in 1965ms:
166 passed in 1.67s
tokens used
5,135,023

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 4 minutes.
Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
Licensed MIT, as reported by its host.
Measured 3 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 by	attempt	outcome	score	cost USD	when
Argusic Runner	3/3	Runs with mocks	92.00	1.01	2026-09-23 23:03 UTC
Argusic Runner	2/3	Runs with mocks	92.00	0.02	2026-09-16 05:19 UTC
Argusic Runner	1/3	Runs with mocks	92.00	0.01	2026-09-11 16:18 UTC

Topics (from GitHub)

google-sheets google-sheets-api google-sheets-api-v4 gspread spreadsheet spreadsheets

Embed the badge

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

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

Questions

Does gspread run?: gspread runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 4 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test gspread?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 7ca71eaa4658. 3 attempts are recorded, and the full method is on the methodology page.
What did it cost to test gspread?: The run that produced this verdict cost $1.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does gspread take to install?: 4 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 gspread need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing gspread?: 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 gspread?: All 3 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.