data-peek
A minimal, fast, database client desktop application. Built for developers who want to quickly peek at their data without the bloat.
Runssource: GitHubhomepageTypeScriptNOASSERTIONcommit 2ce83b15a9a0
TypeScript, NOASSERTION licensed. The project labels itself: database gui, developer tools, electron, hacktoberfest, mcp, mysql, postgresql and sql.
data-peek runs. An Argusic agent installed it in 1.1 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
pnpm install, test suite (1395 passing, 56 skipped), Electron build, and Electron app launch all work; Node 18 compatibility fixes applied for crypto, ES2023 array methods, vitest config loading, and fake timer API usage
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 95.5 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.
- vitest 4 vi.useRealTimers() hangs in afterEach hook on Node 18 when setInterval created under fake timers12 minutes
- vitest 4 config.cjs requires() ESM-only packages (std-env, vite) - fails on Node 188 minutes
- electron-vite build fails: @tailwindcss/oxide native binding not installed (missing optional dependency)4 minutes
- Node.js 18 lacks global crypto.randomUUID in vitest renderer tests3 minutes
- Array.prototype.toSorted is ES2023, not available in Node 182 minutes
- electron-vite build fails: crypto.hash is not a function (Node 21+ API)2 minutes
- Install time
- 1 minutes
- Cold machine to finish
- 37 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- How the result was proved
- npm test (via 'npx vitest run --config vitest.config.mts') returned 83/86 test files passed, 1395/1451 tests passed, 0 failed; Electron app built and launched successfully with all services initialized (schema cache, scheduler, dashboard, notebook storage, time-machine storage, IPC handlers)
- Model tokens used
- 181,540
- Exact commit tested
- 2ce83b15a9a0
- 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.
Total estimated elapsed: ~20 minutes (≈ 1200 seconds) exec /bin/sh -lc '# Count actual duration from the first command echo "Start time (first command): 21:29 UTC" echo "Current time: $(date -u '"'+%H:%M UTC')\"" in /work/repo succeeded in 0ms: Start time (first command): 21:29 UTC Current time: 22:05 UTC About 36 minutes total. tokens used 181,540 About 36 minutes total.
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 1.1 minutes.
- Recovered from all 6 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.
- Measured 4 times, so the result is not a one-off.
What did not, or is not known
- Its license file could not be classified automatically, so check it yourself before using it.
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 1.1 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)
database-guideveloper-toolselectronhacktoberfestmcpmysqlpostgresqlsqlsql-clienttypescript
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/data-peek)Questions
- Does data-peek run?
- Yes. data-peek runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test data-peek?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 2ce83b15a9a0. 4 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test data-peek?
- The run that produced this verdict cost $0.32: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does data-peek take to install?
- 1.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 data-peek need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing data-peek?
- 6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for data-peek?
- All 4 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.