GeoLibre
A lightweight, cloud-native GIS platform for visualizing, exploring, and analyzing geospatial data. It runs in the web browser, on the desktop, on mobile, and inside Jupyter notebooks.
Runssource: GitHubhomepageTypeScriptMITcommit 3bbeb7b38c8a
TypeScript, MIT licensed. The project labels itself: cesium, data science, duckdb, geolibre, geospatial, gis, mapbox and maplibre.
GeoLibre runs. An Argusic agent installed it in 4.5 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
GeoLibre frontend unit tests (10148) and backend Python tests (464) all pass, the production build succeeds, and the Vite dev server responds with HTTP 200.
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.
- Node.js v18.19.1 is installed but project requires Node 22+0.5 minutes
- Node v22.13.0 lacks registerHooks in node:module (needs >=22.18.0)0.5 minutes
- @geolibre/embed dist/ missing — embed-api tests fail with ERR_MODULE_NOT_FOUND0.2 minutes
- npm run test:backend uses python but only python3 is available0.1 minutes
- Install time
- 5 minutes
- Cold machine to finish
- 22 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- npm run test:frontend: 10148 pass, 0 fail, 2 skip; npm run test:backend via venv: 464 pass, 21 skip; npm run build: exit 0, produced dist/; curl http://127.0.0.1:5173/: HTTP 200
- Model tokens used
- 206,292
- Exact commit tested
- 3bbeb7b38c8a
- 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.
- Ran `npm install` with 0 vulnerabilities
- Built the `@geolibre/embed` package (needed for tests)
- Ran all 10,148 frontend unit tests: 10,148 pass, 0 fail, 2 skipped
- Built the backend Python venv with all extras, ran 464 backend tests: 464 pass, 21 skipped (PostG…
- Built the production web app successfully via `npm run build`
- Confirmed the Vite dev server starts and returns HTTP 200 on `localhost:517
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 4…
succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 4.5, "errors": [{"msg": "N…
tokens used
206,292Replay 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.5 minutes.
- Recovered from all 4 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.
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.5 minutes after the clone.
Run history
Topics (from GitHub)
cesiumdata-scienceduckdbgeolibregeospatialgismapboxmaplibremaplibre-gl-jstauri-app
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/geolibre)Questions
- Does GeoLibre run?
- Yes. GeoLibre runs. Argusic installed and launched it on a clean machine in 5 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test GeoLibre?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 3bbeb7b38c8a. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test GeoLibre?
- The run that produced this verdict cost $0.09: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does GeoLibre take to install?
- 4.5 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 GeoLibre need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing GeoLibre?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for GeoLibre?
- 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.