plpgsql_check is a linter tool (does source code static analyze) for the PostgreSQL language plpgsql (the native language for PostgreSQL store procedures).
- plpgsql
- postgresql
- extension
- c
132,241 visible repositories in the index
49–65 of 65 · Most stars
plpgsql_check is a linter tool (does source code static analyze) for the PostgreSQL language plpgsql (the native language for PostgreSQL store procedures).
An extension of RuboCop focused on code performance checks.
PHP Magic Number Detector
A static code analysis tool for Crystal
Detect non-inclusive language in your source code.
Analyzes Elm projects, to help find mistakes before your users find them.
Swiss-army knife for D source code
The Golang linter that checks usage of github.com/stretchr/testify.
Linter for dangerous Postgres migration patterns in Diesel and SQLx. Prevents downtime caused by unsafe schema changes.
Static scope analysis and transpilation of ES6 block scoped const and let variables to ES3 vars
A collection of static analyzers based on Roslyn that integrate with VS
Error Prone extensions: extra bug checkers and a large battery of Refaster rules.
Cross-file drift checker. Keeps code, configs, and docs in sync deterministically. Supports 35+ languages.
Architecture linter for Swift — enforce Clean Architecture import rules via SwiftSyntax. A CI-ready guardrail for AI-assisted development.
Make Java source layout deterministic: reorder class members safely, keep accessors together, format java-source, and enforce style in CI.
Catch broken links before your readers do.
PostgreSQL migration linter. Blocks unsafe migrations before merge: 112 rules, the real Postgres parser, lock analysis, auto-fix. CLI, GitHub Action, MCP.