/cso runs
gstack /cso now tests its fixes against your app in Docker
Comprehensive /cso always fell back to a static audit, because its runtime catalog qualified nothing. Now, with Docker installed, it boots your app in a matching image and tests each finding and repair against it.
Pinned
All ten runtime images ship pinned to a public digest
Node, Bun, Python, Rails and Postgres images are each locked to an exact digest on GitHub's public container registry. Each catalog entry also records its source commit, its software bill of materials, and its provenance.
Bun 1.4.4
Projects that pin Bun 1.4.4 install gstack again
If your project pins Bun 1.4.4, as gbrain now does, the installer stopped with a runtime pin conflict, because it only trusts Bun builds it has checksums for. It now carries 1.4.4, installs it, and finishes clean.
What stays
gstack's own Bun versions stay where they were
The new 1.4.4 checksums cover the same three Linux targets as 1.4.3, checked against Bun's signed release key. gstack's own minimum stays 1.4.2, and its default install stays 1.4.3.
Your pin
The full details are in the gstack changelog
CHANGELOG.md1.91.181.0 · 1.91.182.0Image digests and checksums are in the gstack changelog. Which Bun version does your project pin?
















