Process completed with exit code 2.

lib/Service/ArchiMateImportService.php:5949:34: InvalidArgument: Calling empty on a boolean value is almost certainly unintended (see https://psalm.dev/004)

lib/Service/ArchiMateImportService.php:5947:34: InvalidArgument: Calling empty on a boolean value is almost certainly unintended (see https://psalm.dev/004)

lib/Service/ArchiMateImportService.php:5945:34: InvalidArgument: Calling empty on a boolean value is almost certainly unintended (see https://psalm.dev/004)

lib/Service/ArchiMateImportService.php:5943:27: InvalidArgument: Calling empty on a boolean value is almost certainly unintended (see https://psalm.dev/004)

lib/Service/ArchiMateImportService.php:3250:106: UndefinedFunction: Function OCA\SoftwareCatalog\Service\falsey does not exist (see https://psalm.dev/021)

lib/Service/ArchiMateImportService.php:3250:81: UndefinedThisPropertyFetch: Instance property OCA\SoftwareCatalog\Service\ArchiMateImportService::$isComplexArra is not defined (see https://psalm.dev/041)

lib/Service/ArchiMateExportService.php:2256:80: UndefinedVariable: Cannot find referenced variable $propRef (see https://psalm.dev/024)

lib/Service/ArchiMateExportService.php:1597:31: InvalidArgument: Calling empty on a boolean value is almost certainly unintended (see https://psalm.dev/004)

lib/Service/ArchiMateExportService.php:1552:31: InvalidArgument: Calling empty on a boolean value is almost certainly unintended (see https://psalm.dev/004)

lib/Service/ArchiMateExportService.php:282:23: InvalidArgument: Calling empty on a boolean value is almost certainly unintended (see https://psalm.dev/004)

Process completed with exit code 1.

Process completed with exit code 1.

Unable to resolve path to module '@conduction/nextcloud-vue'

Unable to resolve path to module '@conduction/nextcloud-vue'

Unable to resolve path to module '@conduction/nextcloud-vue'

Unable to resolve path to module '@conduction/nextcloud-vue'

Call to method registerService() on an unknown class OCP\AppFramework\Bootstrap\IRegistrationContext.

Class OCP\App\IAppManager not found.

Class OCP\IUserManager not found.

Class OCP\IGroupManager not found.

Call to method registerService() on an unknown class OCP\AppFramework\Bootstrap\IRegistrationContext.

Parameter $context of method OCA\SoftwareCatalog\AppInfo\Application::register() has invalid type OCP\AppFramework\Bootstrap\IRegistrationContext.

Parameter $context of method OCA\SoftwareCatalog\AppInfo\Application::register() has invalid type OCP\AppFramework\Bootstrap\IRegistrationContext.

OCA\SoftwareCatalog\AppInfo\Application::__construct() calls parent::__construct() but OCA\SoftwareCatalog\AppInfo\Application does not extend any class.

Class OCA\SoftwareCatalog\AppInfo\Application implements unknown interface OCP\AppFramework\Bootstrap\IBootstrap.

Class OCA\SoftwareCatalog\AppInfo\Application extends unknown class OCP\AppFramework\App.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

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/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

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, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

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/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

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, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

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, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

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, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

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/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

Missing JSDoc @PARAM "limit" declaration

Missing JSDoc @PARAM "page" declaration

Defaults are not permitted on @PARAM

Defaults are not permitted on @PARAM

Defaults are not permitted on @PARAM

Defaults are not permitted on @PARAM

The "setup" property should be above the "computed" property on line 59

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, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/