What our run establishes
Zero review: our run recorded a 23-second install. That result supports an installation assessment, while coding quality remains untested. The run took place on 2026-10-07 at commit 99721c7, with full recorded SHA 99721c762f37cd43ac511007a5f51d1846df959e. No new execution was performed for this correction.
Installation returned exit code 0 without timing out. Build and test were separately marked skipped with the reason "no script". Those skipped stages establish neither passing nor failing tests. The overall "ran" status does not establish completion of a coding workload.
The detector selected npm even though it recognized Node and Go and found a Makefile. The pinned README documents Go development checks. Our harness did not run them, so the missing npm scripts say nothing about whether the Go suite passes.
The MrKeyoor testing methodology supplies provenance context. Its current description does not establish that this older run used every procedure it describes.
Installation records disagree
The stored parser summary records 23 seconds for installation, 83 dependency packages and 186 MB on disk. The raw npm footer reports 70 packages added and 71 audited in 14 seconds. The stored summary and raw npm footer disagree on elapsed time and package counts. Their relationship has not been reconciled; we retain both records without attributing the differences to a verified cause. The supplied count-scope warning also says parser summaries do not establish exhaustive unique coverage.
The summary labels the image lab-node:22, while the raw install log identifies Node v18.20.8 and npm 10.8.2. Unsupported-engine warnings show that installation success alone does not demonstrate supported runtime compatibility.
Our recorded npm audit reported 3 advisories: 1 critical and 2 moderate. These are dependency advisories, not demonstrated vulnerabilities in a Zero workflow. The supplied record does not identify affected packages, reachable exploit paths or scannedPackages, so scan coverage is unknown. Investigate the package-level findings before granting access to source credentials. This record does not establish whether a current release still has those findings.
Why consider a supervised trial?
Zero can inspect repositories, edit files, run commands and retain local sessions. The Zero README documents hosted providers alongside Ollama, LM Studio and compatible endpoints. It also describes interactive model selection, resumable sessions and headless text, JSON and stream-JSON operation.
These are documented capabilities. Our run did not connect a provider, submit a coding task, exercise an isolated worktree or validate CI exit behavior. If those capabilities fit your workflow, the next step is one representative task in a disposable repository, followed by an independently checked diff.
Check sandbox guidance against the installed version
The pinned README tells Linux source builders to build zero-linux-sandbox for native sandboxing. Issue 1041 reports reduced isolation after a manual build at a different commit, f30f550. That report is not a sandbox failure observed in our run.
The supplied issue page records closure as completed on October 12, 2026. The current README describes a different helper arrangement: Linux needs Bubblewrap, and the main Zero binary re-executes itself as the helper when zero-linux-sandbox is absent. A separate helper next to the binary or on PATH takes precedence. The historical report therefore cannot establish an unchanged current helper requirement.
Before granting shell or write access, use the documented zero doctor and zero sandbox policy commands to inspect setup and sandbox state. These commands were not executed for this correction, and our stored run did not verify enforcement. Inspecting policy is a preliminary check; it does not replace testing the installed version's behavior.
Alternatives for specific workflows
Codex CLI supports signing in with a ChatGPT account. Its README makes it a candidate replacement when that account-based workflow is your priority. The supplied evidence does not establish stronger isolation or better coding results than Zero.
Aider automatically commits changes with commit messages. Its README also documents linting and testing after changes. Consider it when automatic commits are central to reviewing and undoing edits. We did not compare its results with Zero.
These alternatives answer workflow preferences. The supplied evidence does not establish which tool is faster, safer or cheaper.
What the ratings mean
The ratings are editorial judgments on a 1-5 scale, not benchmark results. Setup ease rates the observed installation path: 1 means installation was blocked, 3 means it completed with unresolved setup caveats, and 5 requires verified operation without material setup barriers. The score is 3 because installation completed with engine warnings and skipped verification.
Documentation rates the specificity of the supplied instructions: 1 means little actionable guidance, 3 means basic setup guidance, and 5 means explicit coverage of installation, providers, headless operation, permissions and development checks. The score is 5 for that coverage, without claiming every instruction was validated.
Community rates visible maintainer engagement in the supplied discussion: 1 means no substantive response in that evidence, 3 means useful guidance, and 5 requires broader evidence of sustained support. The score is 4 because issue 1041 contains substantive maintainer guidance and a recorded resolution. It does not measure adoption or guarantee response times.
Maturity rates the evidence supporting operational confidence: 1 means a demonstrated blocker prevents the evaluated path, 3 requires a representative workload and verification results, and 5 requires substantially broader operational evidence. The score is 2 because installation succeeded, but coding behavior and sandbox enforcement remain untested and the recorded dependency advisories are unresolved in this evidence.

