uudashr / gocognitView external linksLinks
Calculates cognitive complexities of functions (and methods) in Go source code. (Golang cognitive complexity)
☆437Dec 9, 2024Updated last year
Alternatives and similar repositories for gocognit
Users that are interested in gocognit are comparing it to the libraries listed below
Sorting:
- Moved to https://codeberg.org/polyfloyd/go-errorlint☆313Nov 1, 2025Updated 3 months ago
- ☆55Oct 16, 2024Updated last year
- Magic number detector for Go.☆208Dec 21, 2023Updated 2 years ago
- Calculate cyclomatic complexities of functions in Go source code.☆1,532Dec 27, 2025Updated last month
- A Go linter to check that errors from external packages are wrapped☆358Nov 24, 2025Updated 2 months ago
- 🚔 Enforce field tags in (un)marshaled structs☆39Jan 19, 2026Updated 3 weeks ago
- Go linter for forbidding identifiers☆160Oct 25, 2025Updated 3 months ago
- Go linter to detect erroneous multiplication of duration values☆49Oct 24, 2025Updated 3 months ago
- Linter to detects the overuse or misuse of interfaces in Go code AKA "Interface Pollution"☆17Jul 11, 2025Updated 7 months ago
- noctx finds function calls without context.Context.☆216Jul 28, 2025Updated 6 months ago
- ☆43Dec 16, 2024Updated last year
- Go linter that checks if package imports are in a list of acceptable packages.☆194Mar 6, 2025Updated 11 months ago
- Accept Interfaces, Return Concrete Types☆79Dec 15, 2025Updated 2 months ago
- Golang linter to use strconv☆43Nov 19, 2025Updated 2 months ago
- Check that no globals are present in Go code.☆128May 24, 2025Updated 8 months ago
- A linter to ensure that slices are not initialized with non-zero length☆79Oct 25, 2025Updated 3 months ago
- ␊ whitespace linter - Forces you to use empty lines!☆340Updated this week
- ☆121Dec 26, 2025Updated last month
- nakedret is a Go static analysis tool to find naked returns in functions greater than a specified function length.☆132Feb 1, 2026Updated 2 weeks ago
- Find unused parameters in Go☆568Oct 27, 2025Updated 3 months ago
- tparallel finds inappropriate usage of `t.Parallel()` method in your Go test codes☆28Jun 26, 2024Updated last year
- Analyzer: checks whether HTTP response body is closed and a re-use of TCP connection is not blocked.☆323Jan 29, 2026Updated 2 weeks ago
- detects nested contexts in loops or function literals☆65Feb 8, 2026Updated last week
- Analyzer: fourcetypeassert finds type assertions which did forcely☆48Feb 13, 2025Updated last year
- GCI, a tool that control golang package import order and make it always deterministic.☆545Feb 6, 2026Updated last week
- Golang linter to check the errors handling expressions☆67Sep 18, 2025Updated 4 months ago
- Linter that confirms DB rows and statements are closed properly.☆91May 19, 2025Updated 8 months ago
- Check exhaustiveness of switch statements of enum-like constants in Go source code.☆334Dec 5, 2024Updated last year
- 🪵 Ensure consistent code style when using log/slog☆234Feb 8, 2026Updated last week
- Go Dependency Analysis toolkit☆1,593Jan 22, 2026Updated 3 weeks ago
- The most opinionated Go source code linter for code audit.☆2,035Jan 18, 2026Updated 3 weeks ago
- prealloc is a Go static analysis tool to find slice declarations that could potentially be preallocated.☆662Updated this week
- The Golang linter that checks that there is no simultaneous return of `nil` error and an invalid value.☆79Feb 1, 2026Updated 2 weeks ago
- golang analyzer that finds structures with uninitialized fields☆184Jan 9, 2026Updated last month
- Define and run pattern-based custom linting rules.☆862Sep 25, 2025Updated 4 months ago
- Linter that checks that comments end in a period☆48Oct 18, 2025Updated 3 months ago
- golang linter to detect named returns☆29Updated this week
- intrange is a program for checking for loops that could use the Go 1.22 integer range feature.☆36Oct 30, 2025Updated 3 months ago
- Go Linter: finds wasted assignment statements 🗑☆38Dec 2, 2024Updated last year