Skip to content

Code Quality

Code Quality #40

Triggered via schedule April 12, 2026 06:35
Status Failure
Total duration 37s
Artifacts

code-quality.yml

on: schedule
Static Code Analysis
32s
Static Code Analysis
Code Style Check
31s
Code Style Check
Architecture Compliance
31s
Architecture Compliance
Security Analysis
29s
Security Analysis
Documentation Quality
3s
Documentation Quality
Complexity Analysis
24s
Complexity Analysis
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 14 warnings
Complexity Analysis
Process completed with exit code 2.
Complexity Analysis
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires cpsit/typo3-handlebars * -> satisfiable by cpsit/typo3-handlebars[0.5.0, ..., 0.7.26]. - cpsit/typo3-handlebars[0.5.0, ..., 0.7.8] require php ^7.1 || 8.0.* -> your php version (8.2.30) does not satisfy that requirement. - cpsit/typo3-handlebars[0.7.9, ..., 0.7.20] require php >= 7.1 < 8.2 -> your php version (8.2.30) does not satisfy that requirement. - cpsit/typo3-handlebars[0.7.21, ..., 0.7.26] require typo3/cms-core ~10.4.0 || ~11.5.0 -> found typo3/cms-core[v10.4.0, ..., v10.4.37, v11.5.0, ..., v11.5.41] but it conflicts with your root composer.json require (^13.4).
Security Analysis
Process completed with exit code 2.
Security Analysis
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires cpsit/typo3-handlebars * -> satisfiable by cpsit/typo3-handlebars[0.5.0, ..., 0.7.26]. - cpsit/typo3-handlebars[0.5.0, ..., 0.7.8] require php ^7.1 || 8.0.* -> your php version (8.2.30) does not satisfy that requirement. - cpsit/typo3-handlebars[0.7.9, ..., 0.7.20] require php >= 7.1 < 8.2 -> your php version (8.2.30) does not satisfy that requirement. - cpsit/typo3-handlebars[0.7.21, ..., 0.7.26] require typo3/cms-core ~10.4.0 || ~11.5.0 -> found typo3/cms-core[v10.4.0, ..., v10.4.37, v11.5.0, ..., v11.5.41] but it conflicts with your root composer.json require (^13.4).
Architecture Compliance
Process completed with exit code 2.
Architecture Compliance
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires cpsit/typo3-handlebars * -> satisfiable by cpsit/typo3-handlebars[0.5.0, ..., 0.7.26]. - cpsit/typo3-handlebars[0.5.0, ..., 0.7.8] require php ^7.1 || 8.0.* -> your php version (8.2.30) does not satisfy that requirement. - cpsit/typo3-handlebars[0.7.9, ..., 0.7.20] require php >= 7.1 < 8.2 -> your php version (8.2.30) does not satisfy that requirement. - cpsit/typo3-handlebars[0.7.21, ..., 0.7.26] require typo3/cms-core ~10.4.0 || ~11.5.0 -> found typo3/cms-core[v10.4.0, ..., v10.4.37, v11.5.0, ..., v11.5.41] but it conflicts with your root composer.json require (^13.4).
Code Style Check
Process completed with exit code 2.
Code Style Check
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires cpsit/typo3-handlebars * -> satisfiable by cpsit/typo3-handlebars[0.5.0, ..., 0.7.26]. - cpsit/typo3-handlebars[0.5.0, ..., 0.7.8] require php ^7.1 || 8.0.* -> your php version (8.2.30) does not satisfy that requirement. - cpsit/typo3-handlebars[0.7.9, ..., 0.7.20] require php >= 7.1 < 8.2 -> your php version (8.2.30) does not satisfy that requirement. - cpsit/typo3-handlebars[0.7.21, ..., 0.7.26] require typo3/cms-core ~10.4.0 || ~11.5.0 -> found typo3/cms-core[v10.4.0, ..., v10.4.37, v11.5.0, ..., v11.5.41] but it conflicts with your root composer.json require (^13.4).
Static Code Analysis
Process completed with exit code 2.
Static Code Analysis
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires cpsit/typo3-handlebars * -> satisfiable by cpsit/typo3-handlebars[0.5.0, ..., 0.7.26]. - cpsit/typo3-handlebars[0.5.0, ..., 0.7.8] require php ^7.1 || 8.0.* -> your php version (8.2.30) does not satisfy that requirement. - cpsit/typo3-handlebars[0.7.9, ..., 0.7.20] require php >= 7.1 < 8.2 -> your php version (8.2.30) does not satisfy that requirement. - cpsit/typo3-handlebars[0.7.21, ..., 0.7.26] require typo3/cms-core ~10.4.0 || ~11.5.0 -> found typo3/cms-core[v10.4.0, ..., v10.4.37, v11.5.0, ..., v11.5.41] but it conflicts with your root composer.json require (^13.4).
Documentation Quality
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Documentation Quality
Missing @throws annotation in Classes/Service/MediaDataService.php
Documentation Quality
Missing @throws annotation in Classes/DataProcessing/TypoScriptObjectPathProcessor.php
Documentation Quality
Missing @throws annotation in Classes/DataProcessing/TtContent/Field/ImageOrientProcessor.php
Documentation Quality
Missing @throws annotation in Classes/DataProcessing/SerialDataProcessor.php
Documentation Quality
Missing @throws annotation in Classes/DataProcessing/ProcessorVariablesTrait.php
Documentation Quality
Missing @throws annotation in Classes/DataProcessing/CollectionDataProcessor.php
Documentation Quality
Consider adding comprehensive PHPDoc comments
Complexity Analysis
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Security Analysis
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Architecture Compliance
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Code Style Check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Static Code Analysis
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Static Code Analysis
No files were found with the provided path: var/phpstan/. No artifacts will be uploaded.