Report Generated: {{report_end_time}}
Validation Started: {{report_start_time}}
Duration: {{report_duration}}
| Metric | Value | Status |
|---|
Git Branch: {{git_branch_name}}
Warnings for build size, total flows, sub-flows, and components exceeding predefined thresholds.
Highlights potential code quality, best practice, or anti-pattern issues found in Mule flow XML files.
Checks YAML configuration files for syntax errors, schema violations, or missing required fields.
Validates Maven dependencies by checking for missing, unresolved, or duplicate dependencies in all
pom.xml files.
Analyzes Mule flows and sub-flows for complexity, size, and best practices (e.g., too many flows, sub-flows, or components).
Validates API specifications and their implementation, ensuring RAML/OAS files are present and APIkit routers/configs are correctly set up.
Checks if the project uses Mule Secure Properties for sensitive configuration values, promoting secure handling of secrets.
Reviews logger usage in flows and the Log4j configuration for risky patterns (e.g., too many loggers, DEBUG/TRACE levels in production).
Identifies any orphaned flows, sub-flows, or resources not referenced in the project.