Repository navigation
v0.12.32
v0.12.32 — release binaries are built with Go 1.26.10
Every release binary up to v0.12.31 was built with Go 1.26.1, because the build took its Go version from the module's minimum. That toolchain's standard library has 23 known vulnerabilities reachable from logscry's code, fixed in Go 1.26.2 through 1.26.10, most of them in net/http, crypto/tls and crypto/x509: the code logscry uses to reach a remote LLM endpoint over TLS. A local Ollama endpoint was less exposed, but every downloaded binary carried them.
What changed:
- Built with go1.26.10, the latest 1.26 release. The build now pins the toolchain explicitly, and both CI and the release job fail if they ever run with a different Go version.
logscry --versionnow also prints the Go version that built the binary:logscry v0.12.32 (go1.26.10).- CI runs
govulncheckon every change and weekly. It flags any reachable vulnerability that has a fix available, so the next Go patch release cannot go unnoticed. - Installing with
go installstill builds with your own Go toolchain (1.26.1 or newer); use a current one.
Measured:
govulncheck, vulnerabilities reachable from logscry's code in the standard library: 23 with Go 1.26.1, 0 with Go 1.26.10.- In the shipped binaries: 41 standard-library findings in v0.12.31, 0 in a build of this release.
Install: download the binary for your OS from the assets below, or go install github.com/maxie7/logscry/cmd/logscry@latest.
Known limitations:
- #152: the Docker SDK dependency (
github.com/docker/docker) carries daemon-side advisories with no patched version; logscry uses only the client. The migration togithub.com/moby/moby/clientis next. - The full list is in the README's Known limitations.
Tracked as #151.