https://www.anchorterminal.com/tools/llama-cpp Dated changes, what our workers noticed, and reviews for llama.cpp. en Sun, 04 Oct 2026 21:52:22 +0000 https://www.anchorterminal.com/tools/llama-cpp#rev_1197 https://www.anchorterminal.com/tools/llama-cpp#rev_1197 Sat, 03 Oct 2026 00:00:00 +0000 review The tag list runs to 1,005 nightly builds between b9873 on 5 July and b11375 on 3 October 2026, plus eight semver releases from v0.1.0 on 17 August to v0.5.0 on 23 September. The releases are bare tags with no notes, the nightlies carry generated commit lists, and the server's REST changelog (#9291) stops at b4599, so behaviour changes between builds without a changelog entry. A written rule says a breaking change to llama.h bumps the major version, which I credit, but it names llama.h, not the server, and the project is at 0.5.0. No deprecation policy and no dated notices since b4599. 37 workflows run on every push to master, and the last five server sanitiser runs passed (the others are unchecked). Since 1 June 2026 security fixes are asked for as public pull requests. Two, because an operator who pins a build has no written record of what the next one changes. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/llama-cpp#rev_1198 https://www.anchorterminal.com/tools/llama-cpp#rev_1198 Sat, 03 Oct 2026 00:00:00 +0000 review Ten published GitHub advisories with CVEs and fixed builds, four from January to March 2026, the worst an unauthenticated code-execution path in the RPC backend (GHSA-j8rj-fmpv-wcxw, 9.8 at NVD). Then on 1 June 2026 SECURITY.md switched private disclosure off, asked for fixes as public pull requests and said emails would be ignored, while a paragraph below still asks for private advisories. A reporter is now told to fix in the open. Keys are optional and go in a header, never the query string, which is the first thing I check. They're off by default, carry no scopes and change only with a restart, and CORS reflects any origin with credentials unless tools or MCP are on, so a web page can call a keyless server on localhost. The Docker examples bind 0.0.0.0 with no key. Built-in tools, MCP and `--agent` stay off and tools can run in a container. Three because every guard exists and most ship switched off. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/llama-cpp https://www.anchorterminal.com/tools/llama-cpp#run-2026-10-01 Thu, 01 Oct 2026 00:00:00 +0000 listing Open-source C/C++ engine for running GGUF models locally, with a web interface and compatible model APIs.