Yesterday I tested bilawalsidhu/gods-eye-view, the repository that reached the top of GitHub Trending for the global Today view. The project presents a 3D globe with aircraft, ships, satellites, earthquakes, fires, traffic, and public cameras. The demo is visually convincing. The useful question is whether a new user can install it, verify it, and reach the main experience.
The test was pinned to one commit
I pinned commit b22573a9db28e47c324821ebdd4c67bdb241c0e1 and used Linux, Node.js 24.19.0, and npm 11.9.0. The package requirement accepts Node 24.14.x through 24.x or Node 26.x.
The repository is a real application rather than a static demo. The source tree contains 315 files, the scripts directory contains 51 testing and QA files, Vite provides the browser and local proxy layer, and Cesium provides the globe.
Installation and build
I first ran npm ci --ignore-scripts to inspect the dependency installation boundary. After that completed successfully, I ran the official npm ci. Both runs installed 201 packages successfully.
The root project does not define preinstall, install, or postinstall. Several transitive packages still run installation scripts for platform binaries, browser support, or image components. That is normal for this dependency set, but it means the install should not be described as script-free.
npm audit --omit=dev --json reported zero known production-dependency vulnerabilities. A scan for common Google, OpenAI, GitHub, AWS, and private-key patterns found no hard-coded real credentials. These checks reduce obvious risk; they are not a complete security audit.
The production build exited with code 0. Vite finished in 6.67 seconds and generated about 31 MB across 419 files. A few bundles were larger than the configured warning threshold, including the Earth gravity model. The warnings did not block the build.
The test count needs an honest sentence
The official test command reported 2,587 passing assertions. A separate focus-allocation check also passed, bringing the visible total to 2,588 with zero failures.
The process then stayed alive for more than 90 seconds. I had to interrupt it manually, producing exit code 130. The accurate statement is that all visible assertions passed, while the official command did not exit cleanly in this environment. Those two facts belong together in a report.
The main UI is gated by a billable key
With Google, OpenAI, AISStream, Cesium, TomTom, and FIRMS credentials removed, the HTML shell still returned HTTP 200. Several endpoints returned explicit missing-key responses. FIRMS and TomTom status endpoints remained available, and TomTom can fall back to simulated traffic.
The main application follows a different path. Its initialization checks GOOGLE_MAPS_API_KEY and throws when the key is missing. The core 3D globe therefore cannot start without a Google Maps key. The key requires billing and is exposed to the browser bundle, so a real deployment should restrict its referrers, APIs, budget, and quota.
The repository README makes zero-key operation sound broader than the fixed commit actually allows. Zero keys are enough for installation, logical tests, the production build, and selected endpoint checks. They are not enough to enter the main 3D experience.
Browser QA was blocked by the environment
I also ran the track regression command. It found the Puppeteer Chrome binary, but Chrome could not create its process singleton socket in the container and exited with code 2. That is an environment permission failure, not evidence that the map is broken.
It does mean this run did not verify WebGL rendering, map tiles, drag behavior, target focus, or real-data overlays. Those checks remain open until the same application is run in a desktop environment where Chrome and WebGL can start.
Verdict
God’s Eye View is installable and buildable. Its visible test assertions passed, its production dependencies had no known audit findings, and its documentation makes several useful distinctions between live, modeled, reconstructed, and simulated data.
The core user experience still has a hard first-run condition. Without a Google Maps key with billing enabled, the main globe does not initialize. The browser regression is also still pending because of the test container’s socket restriction.
The complete Chinese experiment record, evidence, and author-claim invitation are collected at Jian AI Lab. The source repository is bilawalsidhu/gods-eye-view.
This is a stage-blocked result, not a failure to collect evidence. A useful open-source project can be worth studying even when the first real test ends with a missing credential and an uncompleted browser check.
Top comments (0)