WatermelonDB
🍉 Reactive & asynchronous database for powerful React and React Native apps ⚡️
Runssource: GitHubJavaScriptMITcommit 5c463222ecd7
JavaScript, MIT licensed. The project labels itself: database, hacktoberfest, persistence, react, react native, reactive and rxjs.
WatermelonDB runs. An Argusic agent installed it in 3.7 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
All 80 Jest test suites pass (749 passed, 23 skipped) after npm install --legacy-peer-deps and installing [email protected] to resolve jest-diff/pretty-format version mismatch.
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. 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.
- All 80 test suites failed with TypeError: Cannot read properties of undefined (reading AsymmetricMatcher) in jest-diff1.5 minutes
- npm install failed due to peer dependency conflicts with @testing-library/react-hooks requiring react ^16.9.0 || ^17.0.0 but [email protected] installed1 minute
- Install time
- 4 minutes
- Cold machine to finish
- 4 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- npm test exited 0: 80 suites passed, 749 tests passed, 23 skipped
- Model tokens used
- 70,629
- Exact commit tested
- 5c463222ecd7
- 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.
All tests pass. Let me summarize the findings
exec
/bin/sh -lc 'echo "--- Time check ---" && date' in /work/repo
succeeded in 0ms:
--- Time check ---
Sat Sep 26 22:20:27 UTC 2026
exec
/bin/sh -lc "ARGUSIC_RESULT: echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"inst…
exited 127 in 0ms:
/bin/sh: 1: ARGUSIC_RESULT:: not found
tokens used
70,629Replay 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 3.7 minutes, faster than the median of the 22 comparable projects Argusic has measured.
- 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.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 23 database projects Argusic has installed and timed, WatermelonDB was the 12th fastest to reach a running state, and 19 of 23 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 3.7 minutes after the clone.
Run history
Topics (from GitHub)
databasehacktoberfestpersistencereactreact-nativereactiverxjs
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/watermelondb)Questions
- Does WatermelonDB run?
- Yes. WatermelonDB 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 WatermelonDB?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 5c463222ecd7. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test WatermelonDB?
- The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does WatermelonDB take to install?
- 3.7 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 WatermelonDB need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing WatermelonDB?
- 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 WatermelonDB compare with the alternatives?
- Of the 23 database projects Argusic has installed and timed, WatermelonDB was the 12th fastest to reach a running state, and 19 of 23 reached one at all.
- Where is the evidence for WatermelonDB?
- 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.