Go Analysis Framework Offers Modular Static Analysis for Go Packages. Static analysis inspects a Go package, reports diagnostics such as mistakes or suggested refactorings, and can be invoked by a driver program like vet. A modular analysis processes one package at a time but can retain information from lower‑level packages to use when analyzing higher‑level ones, similar to separate compilation. The printf checker is modular: it records which functions delegate to fmt.Printf and then checks all calls, even those in other packages. The Analyzer type defines an analysis function, its name, documentation, flags and logic. Users create a variable of type Analyzer, for example the unusedresult analyzer, and a driver program imports the required analyzers and adds them to a list. A Pass object supplies the syntax trees, type information and source positions for a single package and provides a Report function to emit diagnostics. Diagnostics are linked to a source position or range and may include a category identifier. To improve efficiency, analyses can use facts—intermediate predicates describing properties of functions or packages. An analysis declares its fact types, and the driver must serialize facts with gob encoding to enable cross‑package sharing. Facts are exported and imported through methods on Pass. The analysistest subpackage lets developers test an Analyzer on sample code, checking that it reports expected diagnostics and facts. Singlechecker and multichecker packages simplify the creation of command‑line tools that run one or multiple analyzers. Future work may extend fact availability to standard library packages, further integrating static analysis into development workflows.