mongo-go-driver
The Official Golang driver for MongoDB
Runs with mockssource: GitHubhomepageGoApache-2.0commit 74620faf2f7b
Go, Apache-2.0 licensed. The project labels itself: database, driver, go, golang, golang library and mongodb.
mongo-go-driver runs, with stand-ins for the services it depends on. An Argusic agent installed it in 6.5 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Go 1.26.8 is installed, the repo builds with go build ./... all short unit tests pass across the entire module
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
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.
- Git submodules not initialized (testdata/specifications missing)4 minutes
- Go 1.26 not found in PATH2.5 minutes
- Test failure in internal/handshake/operation: container metadata detection adds 'runtime:docker' field not expected by test0.5 minutes
- Install time
- 7 minutes
- Cold machine to finish
- 6 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- go build ./... exited 0; go test ./... -short -count=1 with DOCKER_RUNNING=true exited 0 with 38 packages passing
- Model tokens used
- 79,920
- Exact commit tested
- 74620faf2f7b
- 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.
ok go.mongodb.org/mongo-driver/v2/x/mongo/driver/topology 24.807s ok go.mongodb.org/mongo-driver/v2/x/mongo/driver/wiremessage 0.005s ok go.mongodb.org/mongo-driver/v2/x/mongo/driver/xoptions 0.007s All packages pass. Let me also verify build one more time cleanly and get exact tim exec /bin/sh -lc 'export PATH="$HOME/.go/go/bin:$HOME/go/bin:$PATH" && export GOPATH="$HOME/go" && cd /w… succeeded in 1299ms: BUILD OK All tests pass. Let me compile the final report. tokens used 79,920 All tests pass. Let me compile the final report.
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
- Recovered from all 3 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.
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.
- Took 6.5 minutes to install, slower than the median of the 27 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 28 database projects Argusic has installed and timed, mongo-go-driver was the 22nd fastest to reach a running state, and 22 of 28 reached one at all.
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 | 1/3 | Runs with mocks | 92.00 | 0.03 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/mongo-go-driver)Questions
- Does mongo-go-driver run?
- mongo-go-driver runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 7 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test mongo-go-driver?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 74620faf2f7b. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test mongo-go-driver?
- 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 mongo-go-driver take to install?
- 6.5 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 mongo-go-driver need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing mongo-go-driver?
- 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.
- How does mongo-go-driver compare with the alternatives?
- Of the 28 database projects Argusic has installed and timed, mongo-go-driver was the 22nd fastest to reach a running state, and 22 of 28 reached one at all.
- Where is the evidence for mongo-go-driver?
- 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.