HighFile-scopeJava Plug & play

Use `final` for Constants

Ensure that constants are declared with the `final` keyword to prevent modification.

Why this matters

Constants should be declared with `final` to prevent unintended modifications, ensuring immutability and safer code.

Side-by-side examples engineers can pattern-match during review.

Avoid

static int MAX_VALUE = 100;

Prefer

static final int MAX_VALUE = 100;

Bad

static int MAX_VALUE = 100;

Good

static final int MAX_VALUE = 100;

From the same buckets as this rule.

Critical
Avoid Duplicating String Literals
Store repeated string literals in constants or variables to improve maintainability and reduce redundancy.
duplication-complexitymaintainability
Critical
Avoid Empty Methods
Detect methods that have an empty body. If a method is empty, ensure that a comment is present explaining why it remains unimplemented.
maintainabilityreadability-refactor
Critical
Avoid modifying built-in prototypes
Detect modifications to built-in prototypes. Modifying built-in objects can lead to compatibility issues and unexpected behavior. Recommend creating helper functions instead.
maintainabilitysecurity-hardening