Pipeline and Toolkit changes - follow up

Changes to the Service

We would like to inform you about the latest changes and improvements to the service, as well as an upcoming change to the Audit Score enforcement date.

Recent Changes and Improvements:

• Gitleaks added to the corporate pipeline
  Gitleaks has been integrated into the corporate pipeline to strengthen security checks and help identify potential secrets in source code.
• NPM dependencies check
  Complementar check to scan any package.json commited introduced into the corporate pipelines.
• New Toolkit version 10.30.0 released
  The latest Toolkit version includes the following improvements:
  • Improved remove regex functionality with wildcard support.
  • Added support for PHP 8.5.
  • Replaced npm with pnpm and introduced enforcement of the project package lock.
• QA Dashboard improvements
  Several fixes and improvements have been implemented in the QA Dashboard to improve its reliability and user experience.
• Supply-chain hardening
  As of 20 August 2026, the NPM_CONFIG_IGNORE_SCRIPTS variable is enabled by default on the base image. As a result, npm pre/post-install scripts (preinstall, install, and postinstall) will no longer be executed when installing dependencies. This change strengthens protection against software supply-chain risks.
• Blackfire disabled by default
  Since 7 August, the Blackfire check on the corporate pipeline is disabled by default. Projects requiring Blackfire can contact the support team for assistance.

Audit Score Enforcement – New Date

The planned enforcement of the minimum Audit Score on the CD pipeline has been postponed. The new enforcement date is 1 October 2026. From this date, the following rule will apply to all repositories:

• The project must have an Audit Score of at least 85 on the DIGIT-DQA platform.
• Deployments to production environments will be blocked when the Audit Score is below 85.
• Deployments to development, staging, and acceptance environments will continue to operate as today.
• The Audit Score will be re-evaluated on every CD pipeline run.

We recommend reviewing your current Audit Score in advance and addressing any findings that could bring the score below the required threshold.

For any questions or support regarding these changes, please contact the support team.