TYPO3 Extension Conformance Checker

Evaluate TYPO3 extensions against TYPO3 coding standards, architecture patterns, and best practices.

When to Use

• Extension quality / TER readiness
• Scored conformance reports
• Modernization to v12/v13/v14 (v14.3 LTS is default/gold standard)

Delegation

Testing -> typo3-testing | Docs -> typo3-docs | OpenSSF -> enterprise-readiness | Release/TER -> github-release

Raising the extension onto a newer TYPO3 version -> typo3-extension-upgrade, and stop here. Measured: asked to make an extension work with the current LTS, agents loaded this skill instead and delivered a conformance pass — ext_tables.php removed, deprecated calls searched, strict_types counted — then reported done. The manifest still named the old versions and nothing had been installed or tested against the new one. An audit of the current state is not an upgrade, and a widened constraint is not one either. If the request is a version raise, hand it over rather than auditing what is in front of you.

When the request is only to check the version statements and they already agree, say so and stop. Name the range in both notations and the places you compared, and change nothing. Leave out any "minor observations" or "notes, not errors" section: an unrequested remark in a check reads as a finding, and a check that found nothing has nothing else to report.

When composer.json and ext_emconf.php disagree, establish which one is right before making them match. The newest LTS is not the answer by default. Collect the evidence first, then decide: