Quality Areas
Each dbLinter rule belongs to exactly one of 3 software quality areas. Security rules point to code that can be exploited or exposes data, reliability rules to code that can fail or misbehave at run time, and maintainability rules to code that is hard to read, change or review.
Choose a quality area below to explore its rules and examples. Each area page highlights its highest-severity rules first.
Browse by quality area
Security
15 rules. Security is the protection of your software from unauthorized access, use, or destruction.
Maintainability
138 rules. Maintainability refers to the ease with which you can repair, improve and understand software code.
Reliability
76 rules. Reliability is a measure of how your software is capable of maintaining its level of performance under stated conditions for a stated period of time.
Related rule collections
- Trivadis PL/SQL & SQL guideline rules - Rules that implement the Trivadis coding guidelines.
- OWASP-related security rules - Rules that name an OWASP Top 10 risk category.
- Oracle APEX rules - Checks for APEX applications, pages, items and regions.
- PostgreSQL rules - Rules that also apply to PostgreSQL and PL/pgSQL.
- Rules by severity - From Blocker to Info.
- Rule profiles - Essential to Extreme: which rules are checked.
- Rules by tag - Topics such as SQL, performance and naming.
- All rules - Search and filter the complete rule set.