Yes. lowdb runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 0 errors on the way, and recorded the session.

How did Argusic test lowdb?

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

What did it cost to test lowdb?

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 lowdb take to install?

0.1 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 lowdb need a GPU?

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

What goes wrong when installing lowdb?

Nothing did, in the recorded run: zero errors between clone and running.

Where is the evidence for lowdb?

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.

lowdb

Simple and fast JSON database

Runssource: GitHubJavaScriptMITcommit 8a6fce9b72f7

JavaScript, MIT licensed. The project labels itself: database, electron, embeddable, embedded database, javascript, json, localstorage and lodash.

lowdb runs. An Argusic agent installed it in 0.1 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

The lowdb v7.0.1 library installs, builds, and runs all 13 tests successfully; the core Low class, Memory, JSONFile, TextFile adapters, and both async/sync presets work correctly with real file I/O.
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

verdict: Runs
Argusic Score: 100 / 100
cost of the verifying run: $0.01 (measured)
recorded runs: 3
last tested: 2026-09-22
stars: 22,581
forks: 963
open issues: 17
watchers: 241
size: 1 MB
created: 2014-04-02
last push: 2026-03-27

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

Install time: under a minute
Cold machine to finish: 2 minutes
Errors hit and fixed: 0 hit, 0 fixed with no human help
How the result was proved: npm test exited 0, 13 passed; additionally, a programmatic smoke test (write + read via JSONFilePreset) returned the correct data
Model tokens used: 14,397
Exact commit tested: 8a6fce9b72f7
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 2026-09-11. 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.

All tasks completed successfully with no errors. Let me compile the final verdict:
- **Install**: `npm install` succeeded (416 packages), `npm run build` compiled via tsc without err…
- **Tests**: `npm test` ran all 13 tests — all passed (0 fail, 0 skip).
- **Runtime verification**: imported from the built `lib/node.js`, created a `JSONFilePreset`, wrot…
- **Desktop app**: not applicable (this is a library, not a desktop app).
tokens used
14,397
All tasks completed successfully with no errors. Let me compile the final verdict:
- **Install**: `npm install` succeeded (416 packages), `npm run build` compiled via tsc without err…
- **Tests**: `npm test` ran all 13 tests — all passed (0 fail, 0 skip).
- **Runtime verification**: imported from the built `lib/node.js`, created a `JSONFilePreset`, wrot…
- **Desktop app**: not applicable (this is a library, not a desktop app).

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 0.1 minutes, faster than the median of the 13 comparable projects Argusic has measured.
Nothing broke on the way: zero errors between clone and running.
Ran without a GPU, so it does not need one to start.
Licensed MIT, as reported by its host.
Measured 3 times, so the result is not a one-off.

Of the 14 database projects Argusic has installed and timed, lowdb was the 1st fastest to reach a running state, and 13 of 14 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 0.1 minutes after the clone.
Following its own README: the documented path worked with nothing to fix.

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	100.00	0.01	2026-09-22 07:17 UTC
Argusic Runner	2/3	Runs	100.00	0.01	2026-09-15 01:55 UTC
Argusic Runner	1/3	Runs	100.00	0.01	2026-09-11 04:30 UTC

Topics (from GitHub)

database electron embeddable embedded-database javascript json localstorage lodash nodejs storage

Embed the badge

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

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

Questions

Does lowdb run?: Yes. lowdb runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test lowdb?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 8a6fce9b72f7. 3 attempts are recorded, and the full method is on the methodology page.
What did it cost to test lowdb?: 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 lowdb take to install?: 0.1 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 lowdb need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing lowdb?: Nothing did, in the recorded run: zero errors between clone and running.
How does lowdb compare with the alternatives?: Of the 14 database projects Argusic has installed and timed, lowdb was the 1st fastest to reach a running state, and 13 of 14 reached one at all.
Where is the evidence for lowdb?: 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.