The hole
gstack 1.91.159.0 stops the repo it audits from configuring gstack
gstack runs inside the repository it audits, and Bun loaded that repository's .env file. So a committed .env could swap in an attacker's binary and run it as Claude. This release closes that.
The fix
Every Bun that gstack starts now ignores .env and bunfig.toml
A bunfig.toml preload was worse: it ran any code before gstack's first line. Now all 123 Bun entry points skip both files. Your shell environment works exactly as before.
Your config
A repo .env no longer configures gstack
That changes one thing for you. If you kept gstack settings in a repository's .env, gstack ignores them now. Export them in your shell, or set them with gstack-config.
Also
The same isolation reaches evidence runs, builds and Windows
gstack-evidence run now hands its command your shell's environment, as if you ran it by hand, so it stops dropping variables you exported. Compiled builds skip both files, and Windows gets the same isolation.
Your turn
The full notes are in gstack’s changelog
CHANGELOG.mdgstack 1.91.159.0, October 19The details are in gstack's changelog. Do any of the repositories you run gstack in commit a .env file?
