Go by Example
This report summarizes scanner evidence for mmcgrana/gobyexample, a Go project with 8,214 GitHub stars. SynthScan examined 7,311 lines of code across 185 source files, recording 34 pattern matches distributed across 3 syntactic categories. The legacy adjusted pattern signal is 5.2 (Moderate pattern signal); it is not an authorship estimate.
Use the findings to ask whether maintainers can explain intent, verify dependencies, simplify unnecessary scaffolding, and focus review effort. Risk Payload v1 adds ownership, supply-chain, over-engineering, and review-effort vectors when available. These are prompts for human verification, not probabilities, security findings, or measured maintenance costs.
Use each vector to guide manual verification of the underlying findings.
Can maintainers explain intent, assumptions, and trade-offs? 33 finding(s).
Are imports declared and package/API names verified? 1 finding(s).
Are wrappers, guards, and repeated structures necessary? 0 finding(s).
Which changes need focused human review? 34 finding(s).
Run additional scans to build a history of the legacy pattern signal. Score changes are not a measure of AI adoption or code quality.
Groups findings by configured severity weight. Severity is not a confidence estimate, security rating, or proof that a package is missing. Verify imports against the project's manifests and inspect each finding in its local design context.
This horizontal bar chart shows where configured pattern scores accumulate across directories. Treat the bars as locations to inspect, not as evidence of authorship or code quality. Use the file-level findings to decide whether a directory needs a focused ownership, dependency, complexity, or review check.
The scanner identified 34 distinct pattern matches across 3 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a detector match to inspect in context. Expand any category row to inspect the individual file paths, line numbers, code snippets, and the lexical context (CODE, COMMENT, or STRING) in which each match was detected.
Reading the findings table: The Severity column indicates the configured finding weight (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — legacy comment-context matches receive a ×1.5 score weight. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier under the legacy scoring model.
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | examples/maps/maps.go | 41 | // a map. | COMMENT |
| LOW | examples/generics/generics.go | 1 | // Starting with version 1.18, Go has added support for | COMMENT |
| LOW | examples/channel-buffering/channel-buffering.go | 1 | // By default channels are _unbuffered_, meaning that they | COMMENT |
| LOW | examples/slices/slices.go | 41 | // support several more that make them richer than | COMMENT |
| LOW | examples/http-server/http-server.go | 1 | // Writing a basic HTTP server is easy using the | COMMENT |
| LOW | …les-and-directories/temporary-files-and-directories.go | 21 | func main() { | COMMENT |
| LOW | examples/stateful-goroutines/stateful-goroutines.go | 41 | var writeOps uint64 | COMMENT |
| LOW | examples/stateful-goroutines/stateful-goroutines.sh | 1 | # Running our program shows that the goroutine-based | COMMENT |
| LOW | examples/string-formatting/string-formatting.go | 61 | COMMENT | |
| LOW | examples/sha256-hashes/sha256-hashes.sh | 1 | # Running the program computes the hash and prints it in | COMMENT |
| LOW | examples/spawning-processes/spawning-processes.go | 61 | grepIn.Write([]byte("hello grep\ngoodbye grep")) | COMMENT |
| LOW | examples/embed-directive/embed-directive.go | 1 | // `//go:embed` is a [compiler | COMMENT |
| LOW | examples/embed-directive/embed-directive.go | 21 | // Or embed the contents of the file into a `[]byte`. | COMMENT |
| LOW | examples/enums/enums.go | 1 | // _Enumerated types_ (enums) are a special case of | COMMENT |
| LOW | examples/closing-channels/closing-channels.go | 1 | // _Closing_ a channel indicates that no more values | COMMENT |
| LOW | examples/waitgroups/waitgroups.go | 41 | // to propagate errors from workers. For more | COMMENT |
| LOW | examples/execing-processes/execing-processes.go | 21 | // For our example we'll exec `ls`. Go requires an | COMMENT |
| LOW | examples/atomic-counters/atomic-counters.sh | 1 | # We expect to get exactly 50,000 operations. Had we | COMMENT |
| LOW | examples/testing-and-benchmarking/main_test.go | 1 | // Unit testing is an important part of writing | COMMENT |
| LOW | examples/json/json.sh | 21 | # blog post and the [JSON package docs](https://pkg.go.dev/encoding/json/v2) | COMMENT |
| LOW | examples/json/json.go | 81 | // package can put the decoded data. This | COMMENT |
| LOW | examples/pointers/pointers.go | 1 | // Go supports <em><a href="https://en.wikipedia.org/wiki/Pointer_(computer_programming)">pointers</a></em>, | COMMENT |
| LOW | examples/regular-expressions/regular-expressions.go | 21 | // optimized `Regexp` struct. | COMMENT |
| LOW | examples/regular-expressions/regular-expressions.go | 61 | // Our examples above had string arguments and used | COMMENT |
| LOW | examples/exit/exit.go | 21 | // Note that unlike e.g. C, Go does not use an integer | COMMENT |
| LOW | examples/errors/errors.go | 1 | // In Go it's idiomatic to communicate errors via an | COMMENT |
| LOW | examples/command-line-flags/command-line-flags.go | 21 | // and a short description. This `flag.String` function | COMMENT |
| LOW | examples/recover/recover.go | 1 | // Go makes it possible to _recover_ from a panic, by | COMMENT |
| LOW | examples/logging/logging.go | 21 | // `log` package uses the _standard_ logger, which | COMMENT |
| LOW | examples/strings-and-runes/strings-and-runes.go | 21 | // language. Go string literals are UTF-8 | COMMENT |
| LOW | examples/channels/channels.sh | 1 | # When we run the program the `"ping"` message is | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | examples/goroutines/goroutines.go | 36 | // (for a more robust approach, use a [WaitGroup](waitgroups)). | COMMENT |
| MEDIUM | examples/struct-embedding/struct-embedding.go | 2 | // to express a more seamless _composition_ of types. | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | examples/text-templates/text-templates.go | 54 | }{"Jane Doe"}) | CODE |