better-sqlite3
The fastest and simplest library for SQLite3 in Node.js.
Runssource: GitHubJavaScriptMITcommit f8e2d5412082
JavaScript, MIT licensed. The project labels itself: database, sql, sqlite and sqlite3.
better-sqlite3 runs. 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.
better-sqlite3 v13.0.3 builds against bundled SQLite 3.53.4 under Node v24.22.2, its mocha suite passes all 332 tests, and the README example creates a WAL-mode database returning real rows (John Doe, [email protected], count 2).
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.
- System Node.js v18.19.1 does not satisfy engines "node": ">=22"2 minutes
- Mistakenly overwrote the Node SHASUMS256.txt file during download (self-inflicted)1 minute
- Install time
- 4 minutes
- Cold machine to finish
- 2 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- npm run build-debug exited 0 producing build/Debug/better_sqlite3.node; npm test exited 0 with 332 passing (3s); README usage example via node -e returned row 'John Doe [email protected]', count 2, sqlite_version 3.53.4, journal_mode wal
- Model tokens used
- 51,473
- Exact commit tested
- f8e2d5412082
- 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
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
1. Container Node is v18 but `package.json` requires `>=22` → downloaded user-space Node v24.22.2 t… 2. No third-party keys or mocks were needed; verification is tier1 real. tokens used 51,473 Everything is verified. Final state: - Deps installed via `npm install --ignore-scripts` (269 packages, only deprecation warnings) - Native addon built via `npm run build-debug` — exited 0, produced `build/Debug/better_sqlite3.nod… - Test suite via `npm test` — exited 0, **332 passing (3s)**, 0 failing - README usage example executed for real: inserted 2 rows via transaction, `SELECT` returned `John … Errors hit and fixed: 1. Container Node is v18 but `package.json` requires `>=22` → downloaded user-space Node v24.22.2 t… 2. No third-party keys or mocks were needed; verification is tier1 real.
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 4 minutes.
- Recovered from all 2 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.
- Measured 2 times, so the result is not a one-off.
Of the 37 database projects Argusic has installed and timed, better-sqlite3 was the 19th fastest to reach a running state, and 31 of 37 reached one at all.
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 4 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)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/better-sqlite3)Questions
- Does better-sqlite3 run?
- Yes. better-sqlite3 runs. 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 better-sqlite3?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit f8e2d5412082. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test better-sqlite3?
- The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does better-sqlite3 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 better-sqlite3 need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing better-sqlite3?
- 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.
- How does better-sqlite3 compare with the alternatives?
- Of the 37 database projects Argusic has installed and timed, better-sqlite3 was the 19th fastest to reach a running state, and 31 of 37 reached one at all.
- Where is the evidence for better-sqlite3?
- 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.