Upgrade to Pro — share decks privately, control downloads, hide ads and more …

TYPO3 Upgrade Analyzer

TYPO3 Upgrade Analyzer

Avatar for Simon Schaufelberger

Simon Schaufelberger

August 07, 2026

More Decks by Simon Schaufelberger

Other Decks in Technology

Transcript

  1. Facts about me ◉ ◉ ◉ ◉ ◉ Loves surfing

    Loves traveling Lives in The Länd Adventure Educator Loves OpenStreetMap and is a Contributor 3
  2. TYPO3 versions used on the Internet 😱 >80 % use

    outdated versions https://www.t3versions.com/statistics-detail/28 6
  3. “ We completely underestimated the time that we need for

    a TYPO3 Upgrade and needed 2 more weeks and lost a lot of money 9
  4. “ My goal is to help you in the complete

    TYPO3 Upgrade process to make it easier for you to plan and execute it 11
  5. Why everyone needs a TYPO3 Upgrade Analyzer Tool 1. Get

    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
  6. The History of the TYPO3 Upgrade Analyzer ◉ CPS GmbH

    kickstarted the tool in July 2025 ◉ I heard about it through a Rector workshop I gave ◉ I joined the development team in Feb 2026 14
  7. How TYPO3 Upgrade Analyzer works ◉ The TYPO3 Installation is

    inspected ◉ Detect installation type (composer / legacy) ◉ Read installed extension list ◉ Return analyzed result with metrics 16
  8. How TYPO3 Upgrade Analyzer works ◉ Different Analyzers are executed

    ◉ 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
  9. How TYPO3 Upgrade Analyzer works ◉ Metrics are collected and

    passed to a template ◉ A dashboard is generated with summary widgets ◉ Individual report pages are generated with details 18
  10. Continuous Integration of TYPO3 Upgrade Analyzer ./typo3-analyzer analyze rsync -az

    --delete var/reports/html/ \ user@server:/home/www/html/my-report 33
  11. Partnership with DevGuard Continuous Monitoring Instant Alerting False Positive Reduction

    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
  12. 36

  13. 37

  14. Ideas for the future of TYPO3 Upgrade Analyzer ◉ Detect

    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
  15. Qu ote Dev fro day m s 20 There is

    a script for that… 25 “ "git commit" each applied Rule as a single commit with: github.com/mogic-le/rector-single-commit 42
  16. Rector/Fractor single commit script improvements ◉ ◉ ◉ ◉ ◉

    ◉ 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
  17. THANKS! Any questions? Iʼm here to talk with you during

    the dev days! Tell me your ideas / thoughts! 49