orbitdb

Peer-to-Peer Databases for the Decentralized Web

Runssource: GitHubJavaScriptMITcommit 2ee8387240dc

JavaScript, MIT licensed. The project labels itself: crdt, database, decentralized, distributed, ipfs, libp2p, merkle crdt and p2p.

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

OrbitDB @orbitdb/core v4.0.0 installed, all 544 tests pass, and production+debug bundles build successfully on Node.js 22.0.0.

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.03 (measured)
recorded runs
2
last tested
stars
8,826
forks
595
open issues
28
watchers
150
size
18 MB
created
last push

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.

Install time
6 minutes
Cold machine to finish
2 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
npm run test exited 0, 544 passing in 39s; npm run build produced dist/orbitdb.min.js (245 KiB) and dist/orbitdb.js (1.08 MiB) with no failures
Model tokens used
32,708
Exact commit tested
2ee8387240dc
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.

    + 2 modules
webpack 5.89.0 compiled successfully in 597 ms
Everything works flawlessly. Let me now compute the install minutes and prepare the final report.
exec
/bin/sh -lc 'export PATH="$HOME/.n/bin:$PATH" && cd /work/repo && ls dist/' in /work/repo
 succeeded in 0ms:
orbitdb.js
orbitdb.js.map
orbitdb.min.js
orbitdb.min.js.LICENSE.txt
tokens used
32,708

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 6 minutes.
  • 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 2 times, so the result is not a one-off.

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 6 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 byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.03
Argusic Runner1/3Runs100.000.02

Topics (from GitHub)

crdtdatabasedecentralizeddistributedipfslibp2pmerkle-crdtp2ppeer-to-peer

Embed the badge

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

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

Questions

Does orbitdb run?
Yes. orbitdb runs. Argusic installed and launched it on a clean machine in 6 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test orbitdb?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 2ee8387240dc. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test orbitdb?
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 orbitdb take to install?
6 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 orbitdb need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing orbitdb?
Nothing did, in the recorded run: zero errors between clone and running.
Where is the evidence for orbitdb?
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.

Discussion