go-goroutine-auditor

Goroutine leak detection in Go source files is performed by parsing the code to identify `go func()` patterns and evaluating them for missing context cancellation and panic recovery. The audit assigns a risk score to each detected goroutine.

Goroutine leaks in Go applications are typically caused by missing context cancellation, absent panic recovery, and poor lifecycle management. These issues prevent goroutines from terminating properly, which can lead to memory exhaustion and application instability.

Refactoring Go code to use errgroup for concurrency safety involves replacing vulnerable `go func()` patterns with structured errgroup implementations. This provides built-in error handling and lifecycle management for concurrent operations.

Yes, you can use goleak to catch goroutine leaks in a CI CD pipeline by integrating generated goleak test setups. The audit provides these test configurations to automatically detect leaked goroutines during test execution.

The best way to audit Go goroutines for missing panic recovery is to scan the source files for `go func()` launches and assess their risk level. The analysis identifies missing mechanisms and provides refactored code suggestions.

Yes, the goroutine auditing process evaluates existing concurrency code and suggests refactoring using either `errgroup` or `sync.WaitGroup`. This ensures proper lifecycle management regardless of the synchronization primitive used.