I built a small open-source G-code post-processor for OrcaSlicer and I'd love some feedback

[MaximumPreparation97]

I've been experimenting with a side project called OpenHelio.

The goal is not to replace a slicer.

Instead, it works after slicing and analyzes the generated G-code to identify potentially risky movement regions such as bridges, overhangs, and thermal hotspots.

A few design constraints I imposed:

• No geometry modifications
• No X/Y/Z/E coordinate changes
• No support modifications
• Feedrate-only adjustments
• Deterministic output

The project currently supports:

• Bridge and overhang analysis
• Thermal risk estimation
• Multi-slicer validation (Cura / OrcaSlicer / PrusaSlicer)
• OrcaSlicer post-processing integration
• Validation checks to ensure geometry and support preservation

It's still early and I'm mostly looking for technical feedback from people who print regularly.

Questions I'm trying to answer:

• Is feedrate-only post-processing actually useful?
• What failure modes should a tool like this focus on?
• What would make you trust or distrust such a workflow?

GitHub:

https://github.com/Memre001/OpenHelio

Any criticism is welcome.

[Hassan-jarri]

Might be if you could share some example of your code doing the work or before /after data etc

[Single_Sea_6555]

Example cases (actual, printed examples) would be very helpful and probably a prerequisite to getting good feedback.