an overview over extension compatibility ◉ Compatible / incompatible / abandoned / replaced by TYPO3 Core 2. Get an overview over code migrations ◉ What can be done automatically? ◉ What must be done by hand? ▪ Extension Scanner (in the Backend) ▪ Deprecation Logs 3. What needs to be tested by hand? ◉ Manual integration tests 12
◉ Version Availability ◉ Lines of PHP code ◉ Rector migrations ◉ Fractor migrations ◉ Each analyzer is run on certain conditions only ◉ Each analyzer reports its own metrics ◉ Based on the metrics, a score is calculated 17
Track deployed software for newly disclosed vulnerabilities in real time. Automatically create issues when new CVEs affect your software. Eliminate noise with VEX-based assessment sharing. Integrations Risk Prioritization Open Standards Connect with your GitLab or GitHub repos, CI pipelines, and issue trackers. Focus on what matters with improved scoring and exploit probability analysis. Ingest inputs from any scanner or tool that supports open standards. devguard.org 35
Code that canʼt be migrated by Rector ◉ Hooks ◉ … ◉ Link to Changelog file for manual migration ◉ More Analyzers ◉ Notifications about readiness changes ◉ Charts ◉ A scoring system (easy and complex tasks) 38
◉ Colorful Terminal output Dry-Run mode Use ECS/PHP-CS-Fixer for PHP code style fixes Download Commit message files from a repository Prompt for a commit message if file does not exist Preview of applied code changes with option to reject 44