ForgeZero 3.1 “AEGIS” — hardened build toolchain for assembly and C

[alexvoste]

Hello everyone,

I’d like to share ForgeZero, a build toolchain for assembly and C development, written in Go.

The goal is to simplify low-level build workflows by providing a unified CLI over tools like FASM, NASM, GAS, GCC, Clang, LD, and Zig—without Makefiles or complex build scripts.

I’ve just released version 3.1 “AEGIS”.

Recent improvements include:

• native Windows support (no WSL required)
• hardened Virtual FileSystem layer
• verified file access with TOCTOU protection
• secure subprocess execution
• atomic writes and fail-closed verification
• supply-chain integrity improvements
• new

  Code: Select all

  fz doctor

  diagnostics command

Validation:

Code: Select all

go test ./...
go test -race ./...
GOOS=windows go build ./...

Everything passes.

Project:
https://github.com/forgezero-cli/forgezero

I’d especially appreciate feedback from people working on assembly projects, toolchains, or OS development workflows.

[alexvoste]

UPDATE: ForgeZero 4.0 is officially out!

Hey everyone, I just pushed a massive update today — ForgeZero 4.0. While v3.1 focused on hardening, this new release completely overhauls the internal architecture with a focus on raw performance and bare-metal compilation.

What's new in v4.0 for OS Devs:
• Native Flat Binaries: Out-of-the-box support for raw binary output (.bin) without ugly Makefile overrides. Perfect for stage1/stage2 bootloaders.
• 0 Allocs/op Hot Path: Completely re-architected the internal build pipeline in Go to achieve zero heap allocations per operation. It is blindingly fast.
• BLAKE3 Caching: Implemented modern cryptographic file hashing for precise, incremental builds.
• Added the HADES layer for low-level pipeline control.

Check out the updated release notes and benchmarks on GitHub: https://github.com/forgezero-cli/forgezero

Would love to know if anyone has tried using it with custom linker scripts yet!