God’s Eye View was the top project on GitHub Trending when we selected it for Jian AI Lab’s daily experiment.
The pitch is immediately compelling.
It brings aircraft, vessels, satellites, earthquakes, wildfire data, traffic, CCTV sources, and other feeds into one 3D globe.
The repository also makes a serious effort to label data as live, modeled, reconstructed, or simulated.
We tested commit on Linux with Node.js 24.19.0 and npm 11.9.0.
Installation and security checks We first ran , reviewed the install-script sources, and then ran the normal .
Both installations succeeded with 201 packages.
The root project has no preinstall, install, or postinstall hook.
Transitive install scripts come from esbuild, fsevents, Puppeteer, and sharp. reported no known vulnerabilities in production dependencies.
A common secret-pattern scan did not find hard-coded live credentials.
This is a limited check, not a full source audit.
The project talks to many external services, including Google Maps, OpenAI, OpenSky, AISStream, NASA FIRMS, TomTom, CelesTrak, OSM, Open-Meteo, GDELT, and Radio Browser.
It is local-first, but it is not offline.
Server-side keys such as OpenAI and AISStream are read by the local Vite proxy.
Google Maps and Cesium tokens are intentionally delivered to the browser.
Users must restrict referrers and APIs and set provider budgets and quotas. 2,588 visible assertions passed The main test suite reported 2,587 passing assertions and zero failures.
A separate focus-allocation check added one more passing assertion.
The visible total was 2,588 passes and zero failures.
The process did not exit after the summary.
We waited more than 90 seconds and interrupted it manually.
The final exit code was
130.
The precise result is that all visible assertions passed, while the official test command did not complete with a clean exit in this environment.
This may indicate an open handle, connection, or child process that remains alive after the tests finish.
The production build succeeded completed with exit code 0 in 6.67 seconds.
The directory contained 419 files and was about 31 MB.
Vite reported browser externalization warnings for two Node modules and warned about several bundles larger than 1.5 MB.
The warnings did not block the build, but initial-load performance deserves a separate measurement.
The core 3D interface requires a Google Maps key We cleared the Google, OpenAI, AIS, Cesium, TomTom, and FIRMS environment variables before starting the local server.
The HTML shell returned HTTP
200.
Missing-key API routes behaved clearly.
OpenAI, Google Places, and AISStream returned explicit 503 responses.
FIRMS and TomTom status routes remained available, and traffic can fall back to a simulation without a TomTom key.
The main UI is different. checks during initialization and throws when it is absent.
The interactive globe never becomes available.
The key must have the required Google Maps service enabled and billing turned on.
Because it is visible in the browser, it also needs strict referrer and API restrictions plus a budget and quota policy.
Without that key, a user can install the repository, run logic tests, build the production bundle, and inspect several status endpoints.
They cannot enter the core photorealistic 3D experience.
Browser and WebGL QA remain incomplete The repository includes a regression command.
After starting the server, the script found Puppeteer’s downloaded Chrome.
Chrome then crashed because the current container could not create its process-singleton socket.
The command exited with code
2.
This is an execution-environment restriction, not an application assertion failure.
It also means we did not verify WebGL, real map tiles, dragging, target focus, or live data accuracy.
Completing that stage requires a desktop environment that can run Chrome and WebGL, plus a billing-enabled Google Maps key with strict restrictions.
Verdict God’s Eye View has a substantial engineering foundation.
Installation and product