Skip to content

feat: [DTOSS-12154] disabled shared access key for storage account and enabled use managed identity for storage account #15493

feat: [DTOSS-12154] disabled shared access key for storage account and enabled use managed identity for storage account

feat: [DTOSS-12154] disabled shared access key for storage account and enabled use managed identity for storage account #15493

Triggered via pull request April 30, 2026 12:47
Status Success
Total duration 15m 53s
Artifacts 125

cicd-1-pull-request.yaml

on: pull_request
Set CI/CD metadata
8s
Set CI/CD metadata
Validate PR title
6s
Validate PR title
Commit stage  /  Scan secrets
18s
Commit stage / Scan secrets
Commit stage  /  Check file format
8s
Commit stage / Check file format
Commit stage  /  Check Markdown format
8s
Commit stage / Check Markdown format
Commit stage  /  Check English usage
10s
Commit stage / Check English usage
Commit stage  /  Lint Terraform
7s
Commit stage / Lint Terraform
Commit stage  /  Count lines of code
8s
Commit stage / Count lines of code
Test stage  /  Check for consolidated test project
7s
Test stage / Check for consolidated test project
Test stage  /  Run consolidated tests
1m 58s
Test stage / Run consolidated tests
Test stage  /  Get unit test scopes
0s
Test stage / Get unit test scopes
Matrix: Test stage / Unit tests
Test stage  /  Aggregate results and report
28s
Test stage / Aggregate results and report
Analysis stage  /  Perform static analysis
6m 33s
Analysis stage / Perform static analysis
Image build stage  /  get-functions
6s
Image build stage / get-functions
Image build stage  /  build-base-images
2m 0s
Image build stage / build-base-images
Matrix: Image build stage / build-and-push
Image build stage  /  aggregate-json
11s
Image build stage / aggregate-json
Matrix: deploy-stage / Deploy
Waiting for pending jobs
Fit to window
Zoom out
Zoom in

Annotations

107 warnings
Validate PR title
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: amannn/action-semantic-pull-request@v5. 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/
Commit stage / Count lines of code
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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/
Test stage / Run consolidated tests
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/setup-dotnet@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/
Test stage / Run consolidated tests: application/CohortManager/src/Functions/Shared/dotnet-mesh-client/application/DotNetMeshClient/NHS.Mesh.Client/Models/Response/OutboxService/TrackOutboxResponse.cs#L27
Non-nullable property 'RecipientOrgName' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Test stage / Run consolidated tests: application/CohortManager/src/Functions/Shared/dotnet-mesh-client/application/DotNetMeshClient/NHS.Mesh.Client/Models/Response/OutboxService/TrackOutboxResponse.cs#L25
Non-nullable property 'RecipientOrgCode' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Test stage / Run consolidated tests: application/CohortManager/src/Functions/Shared/dotnet-mesh-client/application/DotNetMeshClient/NHS.Mesh.Client/Models/Response/OutboxService/TrackOutboxResponse.cs#L23
Non-nullable property 'RecipientOdsCode' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Test stage / Run consolidated tests: application/CohortManager/src/Functions/Shared/dotnet-mesh-client/application/DotNetMeshClient/NHS.Mesh.Client/Models/Response/OutboxService/TrackOutboxResponse.cs#L21
Non-nullable property 'RecipientName' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Test stage / Run consolidated tests: application/CohortManager/src/Functions/Shared/dotnet-mesh-client/application/DotNetMeshClient/NHS.Mesh.Client/Models/Response/OutboxService/TrackOutboxResponse.cs#L19
Non-nullable property 'Recipient' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Test stage / Run consolidated tests: application/CohortManager/src/Functions/Shared/dotnet-mesh-client/application/DotNetMeshClient/NHS.Mesh.Client/Models/Response/OutboxService/TrackOutboxResponse.cs#L17
Non-nullable property 'UploadTimestamp' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Test stage / Run consolidated tests: application/CohortManager/src/Functions/Shared/dotnet-mesh-client/application/DotNetMeshClient/NHS.Mesh.Client/Models/Response/OutboxService/TrackOutboxResponse.cs#L15
Non-nullable property 'ExpiryTime' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Test stage / Run consolidated tests: application/CohortManager/src/Functions/Shared/dotnet-mesh-client/application/DotNetMeshClient/NHS.Mesh.Client/Models/Response/OutboxService/TrackOutboxResponse.cs#L13
Non-nullable property 'FileName' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Test stage / Run consolidated tests: application/CohortManager/src/Functions/Shared/dotnet-mesh-client/application/DotNetMeshClient/NHS.Mesh.Client/Models/Response/OutboxService/TrackOutboxResponse.cs#L7
Non-nullable property 'MessageId' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Test stage / Run consolidated tests: application/CohortManager/src/Functions/Shared/dotnet-mesh-client/application/DotNetMeshClient/NHS.Mesh.Client/Configuration/MeshConnectConfiguration.cs#L51
Non-nullable property 'ProxyAddress' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Test stage / Aggregate results and report
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@v4, bibipkins/dotnet-test-reporter@v1.5.3. 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/
Analysis stage / Perform static 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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@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/
Analysis stage / Perform static analysis: application/CohortManager/src/Functions/Shared/dotnet-mesh-client/application/DotNetMeshClient/NHS.Mesh.Client/Models/MessageMetaData.cs#L5
Non-nullable property 'WorkflowID' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Analysis stage / Perform static analysis: application/CohortManager/src/Functions/Shared/dotnet-mesh-client/application/DotNetMeshClient/NHS.Mesh.Client/Models/MeshResponse.cs#L8
Non-nullable field 'Response' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.
Analysis stage / Perform static analysis: application/CohortManager/src/Functions/Shared/dotnet-mesh-client/application/DotNetMeshClient/NHS.Mesh.Client/Configuration/MeshConnectConfiguration.cs#L51
Non-nullable property 'ProxyAddress' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Image build stage / build-base-images
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3. 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/
Image build stage / build-and-push (wiremock)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. 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/
Image build stage / build-and-push (wiremock)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
Image build stage / build-and-push (db-migration)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. 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/
Image build stage / build-and-push (db-migration)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
Image build stage / build-and-push (gene-code-lkp-data-service)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. 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/
Image build stage / build-and-push (gene-code-lkp-data-service)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
Image build stage / build-and-push (update-blocked-flag)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. 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/
Image build stage / build-and-push (update-blocked-flag)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
Image build stage / build-and-push (remove-dummy-gp-code)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. 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/
Image build stage / build-and-push (remove-dummy-gp-code)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
Image build stage / build-and-push (reference-data-service)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. 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/
Image build stage / build-and-push (reference-data-service)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
Image build stage / build-and-push (participant-management-data-service)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. 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/
Image build stage / build-and-push (participant-management-data-service)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
Image build stage / build-and-push (servicenow-cases-data-service)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. 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/
Image build stage / build-and-push (web)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. 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/
Image build stage / build-and-push (servicenow-cases-data-service)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
Image build stage / build-and-push (web)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
Image build stage / build-and-push (process-nems-update)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. 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/
Image build stage / build-and-push (process-nems-update)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
Image build stage / build-and-push (remove-validation-exception-data)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. 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/
Image build stage / build-and-push (remove-validation-exception-data)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
Image build stage / build-and-push (retrieve-cohort-distribution-data)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. 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/
Image build stage / build-and-push (retrieve-cohort-distribution-data)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
Image build stage / build-and-push (cohort-distribution-data-service)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. 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/
Image build stage / build-and-push (cohort-distribution-data-service)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
Image build stage / build-and-push (manage-servicenow-participant)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. 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/
Image build stage / build-and-push (manage-servicenow-participant)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
Image build stage / build-and-push (exception-management-data-service)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. 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/
Image build stage / build-and-push (exception-management-data-service)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
Image build stage / build-and-push (update-exception)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. 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/
Image build stage / build-and-push (update-exception)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
Image build stage / build-and-push (retrieve-cohort-request-audit)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. 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/
Image build stage / build-and-push (retrieve-cohort-request-audit)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
Image build stage / build-and-push (nems-subscription-data-service)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. 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/
Image build stage / build-and-push (nems-subscription-data-service)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
Image build stage / build-and-push (nems-mesh-retrieval)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. 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/
Image build stage / build-and-push (nems-mesh-retrieval)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
Image build stage / build-and-push (retrieve-pds-demographic)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. 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/
Image build stage / build-and-push (retrieve-pds-demographic)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
Image build stage / build-and-push (manage-caas-subscription)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. 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/
Image build stage / build-and-push (manage-caas-subscription)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
Image build stage / build-and-push (static-validation)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. 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/
Image build stage / build-and-push (static-validation)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
Image build stage / build-and-push (manage-participant)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. 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/
Image build stage / build-and-push (manage-participant)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
Image build stage / build-and-push (lookup-validation)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. 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/
Image build stage / build-and-push (lookup-validation)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
Image build stage / build-and-push (transform-data-service)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. 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/
Image build stage / build-and-push (transform-data-service)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
Image build stage / build-and-push (bs-request-audit-data-service)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. 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/
Image build stage / build-and-push (bs-request-audit-data-service)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
Image build stage / build-and-push (manage-nems-subscription)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. 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/
Image build stage / build-and-push (manage-nems-subscription)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
Image build stage / build-and-push (receive-caas-file)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. 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/
Image build stage / build-and-push (receive-caas-file)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
Image build stage / build-and-push (screening-lkp-data-service)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. 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/
Image build stage / build-and-push (screening-lkp-data-service)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
Image build stage / build-and-push (audit-writer)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. 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/
Image build stage / build-and-push (audit-writer)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
Image build stage / build-and-push (retrieve-mesh-file)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. 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/
Image build stage / build-and-push (retrieve-mesh-file)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
Image build stage / build-and-push (delete-participant)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. 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/
Image build stage / build-and-push (delete-participant)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
Image build stage / build-and-push (servicenow-cohort-lookup)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. 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/
Image build stage / build-and-push (servicenow-cohort-lookup)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
Image build stage / build-and-push (distribute-participant)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. 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/
Image build stage / build-and-push (distribute-participant)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
Image build stage / build-and-push (servicenow-message-handler)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. 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/
Image build stage / build-and-push (servicenow-message-handler)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
Image build stage / build-and-push (durable-demographic-function)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. 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/
Image build stage / build-and-push (durable-demographic-function)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
Image build stage / build-and-push (create-exception)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. 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/
Image build stage / build-and-push (create-exception)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
Image build stage / build-and-push (get-validation-exceptions)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. 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/
Image build stage / build-and-push (get-validation-exceptions)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
Image build stage / build-and-push (participant-demographic-data-service)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. 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/
Image build stage / build-and-push (participant-demographic-data-service)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
Image build stage / build-and-push (higher-risk-referral-reason-lkp-data-service)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. 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/
Image build stage / build-and-push (higher-risk-referral-reason-lkp-data-service)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
Image build stage / aggregate-json
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@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/

Artifacts

Produced during runtime
Name Size Digest
aggregated-sbom-repository-report-pr1882.zip
10.9 MB
sha256:3dde1580a458f96caee971f1eaf90c438ba4a647d14fccbd0453201025e333c8
aggregated-vulnerabilities-repository-report-pr1882.zip
592 KB
sha256:51bfca6de831add1c94cf8e066c4878e7ca82732d7ff87ff338b7ddc25e8e796
cohort-manager-audit-writer-vulnerabilities-summary.txt
2.26 KB
sha256:b8179fc6040b4e60c5cfe498c8266fa3a09539a285991d7aecb72eeb07950b1b
cohort-manager-bs-request-audit-data-service-vulnerabilities-summary.txt
2.31 KB
sha256:8b1fb52d8a71603c32289065f1db8477c7bbc41aa5e574d9934c983b018302b6
cohort-manager-cohort-distribution-data-service-vulnerabilities-summary.txt
2.31 KB
sha256:dd27741d0e38b86ba38ff2fb6fb2c84d0eabb292545535291982524bc67bc53f
cohort-manager-create-exception-vulnerabilities-summary.txt
2.27 KB
sha256:b0a5dda5f0d9577a0d297d4c7675db6d9cf1a9d0ef5107b4d7607fc36304dce6
cohort-manager-db-migration-vulnerabilities-summary.txt
1.73 KB
sha256:d0f365c517efe1b73e05140eb70c931b04652bc88254ffedecb53bab1d7d4a65
cohort-manager-delete-participant-vulnerabilities-summary.txt
2.28 KB
sha256:5a9139a19b07408f8be955d2f7e663e5d5af1f81faf0dafa36d61d3a36aec9ae
cohort-manager-distribute-participant-vulnerabilities-summary.txt
2.29 KB
sha256:ba82031ef35ac35496a3237f4f538f95773c5593e3fa684e3fb72d2b08680d3a
cohort-manager-durable-demographic-function-vulnerabilities-summary.txt
2.31 KB
sha256:0c7b3ca3de678a7d7b9c8050fee6f474f440c09a5509f130cb45aefc6c5e46de
cohort-manager-exception-management-data-service-vulnerabilities-summary.txt
2.31 KB
sha256:0475c9f25b067318acbe4b77b81b3ae7609593de1d7dc61f2b3f8c4b38e34263
cohort-manager-gene-code-lkp-data-service-vulnerabilities-summary.txt
2.3 KB
sha256:9b3432d4b763c4c9ecd5057cdf39a92218f010db01453a08e43a8849904b35c2
cohort-manager-get-validation-exceptions-vulnerabilities-summary.txt
2.29 KB
sha256:c76806455b5786ffc11fa9df329865af06b3794fb5d5fa2f7e273b034a2768e2
cohort-manager-higher-risk-referral-reason-lkp-data-service-vulnerabilities-summary.txt
2.35 KB
sha256:8084dcf8abd70e70118827e679d13af5d44f0b145f9c105ad8c608cf968bbce1
cohort-manager-lookup-validation-vulnerabilities-summary.txt
2.27 KB
sha256:3a61e06a28e2477649c545ad4af4702bc85bb614d6f20232f5c29e99981d759f
cohort-manager-manage-caas-subscription-vulnerabilities-summary.txt
2.29 KB
sha256:d84888ef635feca21e49ba33e37c1f4cbe79d468d2dfd06f5f6bcd353a2927e3
cohort-manager-manage-nems-subscription-vulnerabilities-summary.txt
2.29 KB
sha256:b242cc9b908c004f456499c2e62bd65c00efaedd15b91e548f90ff3e91873888
cohort-manager-manage-participant-vulnerabilities-summary.txt
2.27 KB
sha256:d372b067186d9324c1010544c67a2f9e8772bc721e655eac454b429399d17170
cohort-manager-manage-servicenow-participant-vulnerabilities-summary.txt
2.3 KB
sha256:7b96706a4be29b614c37d99f6778db0ba4cff647f7fa92680a16b7b5af4c1a9d
cohort-manager-nems-mesh-retrieval-vulnerabilities-summary.txt
2.28 KB
sha256:9939c17e788d34ec97d21012147974d5309b6369bae646b1a8df9222c4301fcc
cohort-manager-nems-subscription-data-service-vulnerabilities-summary.txt
2.31 KB
sha256:a29d5ed7423c66ecd5c1833cf502dfe8aa10ef78c190418c08ef5199b925c00d
cohort-manager-participant-demographic-data-service-vulnerabilities-summary.txt
2.32 KB
sha256:bea7e2c2cdc584801cb08f5d09773b110f3360f2f911edcbd27ea2af6123fb7d
cohort-manager-participant-management-data-service-vulnerabilities-summary.txt
2.32 KB
sha256:6d3c38d746fb24eb614d0e6f7cd95c4893c6d757b24d33960bf97a6d6d3b8233
cohort-manager-process-nems-update-vulnerabilities-summary.txt
2.28 KB
sha256:8f5c0d6c7c04a40147d7cdfee66e7add5bb44b4d92ad465eae835ffcd8fabf76
cohort-manager-receive-caas-file-vulnerabilities-summary.txt
2.27 KB
sha256:a9e55c371c9319ff594acfca60ffa8d3d613094b66ee2f5c6d04646094c2bd48
cohort-manager-reference-data-service-vulnerabilities-summary.txt
2.29 KB
sha256:6d1629f649e0f9fdef71a9866418e9785311454df7b9557329f3121693f17f74
cohort-manager-remove-dummy-gp-code-vulnerabilities-summary.txt
2.28 KB
sha256:2f1a782e8bf3dfbf18198164013fa189ce8b1939e36d58032a06225447515d3a
cohort-manager-remove-validation-exception-data-vulnerabilities-summary.txt
2.31 KB
sha256:ba26d1b3e8dddb6945d9ac6e65d51e6553cf82c7f9e56f1e02a9960c3b8e5b7c
cohort-manager-retrieve-cohort-distribution-data-vulnerabilities-summary.txt
2.31 KB
sha256:3e4873b3346f57976a5f424792db1acd7c5c9b668ccedd3ee3c7231058f74856
cohort-manager-retrieve-cohort-request-audit-vulnerabilities-summary.txt
2.3 KB
sha256:f9f53fc95e2758424fc664c58a749bda7956b0e11feea895261a4acf70e9b80b
cohort-manager-retrieve-mesh-file-vulnerabilities-summary.txt
2.28 KB
sha256:9cb11cfd7f0a72a12f79eb21c6f6098ccb44ac21d63eab753331b66b835e0ba4
cohort-manager-retrieve-pds-demographic-vulnerabilities-summary.txt
2.29 KB
sha256:f5fb24771af059f0b1b5b2e8bddab28a26ce8cd01d7cbd8b3c135c7c4e5843a4
cohort-manager-screening-lkp-data-service-vulnerabilities-summary.txt
2.3 KB
sha256:b5f5977780f803dc973bdccf46b1e73d518e5cab160ebd7ebc91187283df2208
cohort-manager-servicenow-cases-data-service-vulnerabilities-summary.txt
2.3 KB
sha256:df12623f300c93e2c675be36e3953157d38a23a4919ac7ee1252aee3f7084042
cohort-manager-servicenow-cohort-lookup-vulnerabilities-summary.txt
2.29 KB
sha256:0f2e5c7852d7828cc2d4621823e3e89d7915d028add2bdd5d183f9292465d565
cohort-manager-servicenow-message-handler-vulnerabilities-summary.txt
2.3 KB
sha256:ae77d82ade7906010e670ceec96961887ecf15b9766f639cd21445a240dfc696
cohort-manager-static-validation-vulnerabilities-summary.txt
2.27 KB
sha256:6434fd7901b906df2698a63236106721b968eda55a5b811fa6f967ab86e8ade6
cohort-manager-transform-data-service-vulnerabilities-summary.txt
2.29 KB
sha256:63a8ebfbf48f47eb84e3513ed0a7ee7449b606881f03996bdf85a44c74c40cd6
cohort-manager-update-blocked-flag-vulnerabilities-summary.txt
2.28 KB
sha256:2dcff7ebd5a74d743d6c3f8a7dd4cc5f6364e32ea2e8568e1dc181af277dde5c
cohort-manager-update-exception-vulnerabilities-summary.txt
2.27 KB
sha256:9e2832d1bc7ab04589dba17098b3711f8d58feca27fd4933bae76d67299c6374
cohort-manager-web-vulnerabilities-summary.txt
511 Bytes
sha256:332b145d8038615f98b4b4b6d1c590e5b0312c56fdaf2ff2f57fde12f211dd5f
cohort-manager-wiremock-vulnerabilities-summary.txt
1.59 KB
sha256:120cff68941fdc6a9efdabed98f74dd86d677300d51cb157d4f538f9b9dab71d
lines-of-code-report.json.zip
994 Bytes
sha256:236f794b0a401adb976807cc5d6ed232fb5800be11637d33fcc770f01333cf45
sbom-audit-writer-repository-report.json.zip
279 KB
sha256:8c63cb9244b4c0b13ae83c0bec7c092c8cbb142ab0fe14398a5614d104f57faf
sbom-bs-request-audit-data-service-repository-report.json.zip
279 KB
sha256:0b01868cc9f6e8700ece1c5f6560ca649aa167e5889f81f9d682fa4f578708e7
sbom-cohort-distribution-data-service-repository-report.json.zip
279 KB
sha256:e6fdea56316fcb7ff696dea4c6af0a55226dc7fefe10680cb34ab4c404454b0e
sbom-create-exception-repository-report.json.zip
279 KB
sha256:455e74e90fd59eca49938546beb2e300c92c4a50ab33b9e88baf045e7ae0ad97
sbom-db-migration-repository-report.json.zip
279 KB
sha256:7be7287f2b2cd4538e38d24a4e76d5e2a5ae9dd245ca68194d16cd571c776eed
sbom-delete-participant-repository-report.json.zip
279 KB
sha256:acb7963d56a4d7c0151db3eff3d80cc98dc92610073ef9c942d019bf616f0851
sbom-distribute-participant-repository-report.json.zip
279 KB
sha256:4124dc8ad59e5a622b136a1fed5d9315c7dd9b8f00c073883e9ac594cd2472f0
sbom-durable-demographic-function-repository-report.json.zip
279 KB
sha256:6e346b423f5e3a408b4a50f12c4af89a5fb6c8d51bd7473bb0f5db3664c9181d
sbom-exception-management-data-service-repository-report.json.zip
279 KB
sha256:27926035379ae6b58938984b3799b8dda9e69262d1de6ceb79046292b669a715
sbom-gene-code-lkp-data-service-repository-report.json.zip
279 KB
sha256:cb96b4f318d0b31defd7fbf3ada9923f5a8317888a1237f0d66f15ae2ca2fffa
sbom-get-validation-exceptions-repository-report.json.zip
279 KB
sha256:d6b145aa686215722a512ceafb72c78f3de873e04df941d41d3ec38a563df299
sbom-higher-risk-referral-reason-lkp-data-service-repository-report.json.zip
279 KB
sha256:b821635ca35e1c66d25462f203596f61692b11e413ae10dac6cac5818538e3bb
sbom-lookup-validation-repository-report.json.zip
279 KB
sha256:632f568167628a88c18234f35ea99bcf39531238ad8ac00042c96c6885353275
sbom-manage-caas-subscription-repository-report.json.zip
279 KB
sha256:c55c6eb518e5380001b5d8c1579a619cb18197ab727b428707610e3e214e2151
sbom-manage-nems-subscription-repository-report.json.zip
279 KB
sha256:961233eadff24e595d9c938276678ca8b86767e36fb5599d2215d0771aceb36d
sbom-manage-participant-repository-report.json.zip
279 KB
sha256:48f40543aae13ee37530170851d04747a8e669167e8f1d59004c1612904ad3ea
sbom-manage-servicenow-participant-repository-report.json.zip
279 KB
sha256:eff9a463874664edf014dbc182886503b89aec04dd7ef0dbf49c6d54cb6eb807
sbom-nems-mesh-retrieval-repository-report.json.zip
279 KB
sha256:5f1d20b9c6538c46121557e560b70cd6082de9081c07828c6eb7de35b6ec6124
sbom-nems-subscription-data-service-repository-report.json.zip
279 KB
sha256:7c1e416b7e52fcd918575a02edd9d8107a77bc0404ebf7a81caaf7f3ae8a74e5
sbom-participant-demographic-data-service-repository-report.json.zip
279 KB
sha256:9926f52791d22b7da3683f6609419c9045d77a5558694a6b06bceabbbe00d4f0
sbom-participant-management-data-service-repository-report.json.zip
280 KB
sha256:9b2644fb31d713f914113ed8437397d3df87cac15d3a2d277ce05df839c97042
sbom-process-nems-update-repository-report.json.zip
279 KB
sha256:24677e55cfeffcd8e9450c5ed3efbd7c08561717d0def3c534d3fab30aea5d74
sbom-receive-caas-file-repository-report.json.zip
279 KB
sha256:da19a0b485218074b0ca5427e2679abe930ca32ca26eb753dbb4ab617ec9a47c
sbom-reference-data-service-repository-report.json.zip
279 KB
sha256:23dce383ee009cc70159101fbbea6312b2dd5ef60800139c1ed8c5b0b41616a0
sbom-remove-dummy-gp-code-repository-report.json.zip
279 KB
sha256:84fe5231342395fdd225f02907072dc8136fd9fb435727a8e99c5aef4ae7c3f6
sbom-remove-validation-exception-data-repository-report.json.zip
279 KB
sha256:73e92592c0fcf1281f313330543792bdee3510b430b982d521f63ad831459479
sbom-retrieve-cohort-distribution-data-repository-report.json.zip
279 KB
sha256:0568a1a7d69dffd822eda8531641c019640ac7e2205b5cfe977bd29b51fd26f5
sbom-retrieve-cohort-request-audit-repository-report.json.zip
279 KB
sha256:812b7af8edc5af091389039b3551659b22cde5ca6a88e8a35e0cae92686bb083
sbom-retrieve-mesh-file-repository-report.json.zip
279 KB
sha256:5061f28cc3b34400f89451ed7f9bcb50b6cc0434248df29cdd9a5941e50965bc
sbom-retrieve-pds-demographic-repository-report.json.zip
279 KB
sha256:394c6712d94acce80009afd6ce416ff485e805bb7f0e382990a1d54c304abdd2
sbom-screening-lkp-data-service-repository-report.json.zip
279 KB
sha256:f692730adcfd8b9ac1799dd2f027c939ec58b0d6251e623ac02d8080c1a8d1b1
sbom-servicenow-cases-data-service-repository-report.json.zip
279 KB
sha256:d92ca65a7cb0e11ce0afc8445e64f417ce957c29192563ac167754139e44b462
sbom-servicenow-cohort-lookup-repository-report.json.zip
279 KB
sha256:ace9bf6039508651b4558b6c801bf9b90c0bb96cf78cc1aabecbd2a74124bd81
sbom-servicenow-message-handler-repository-report.json.zip
279 KB
sha256:6fbf121c82c58f42d1c09f7147963ea58bc2c28ab1bb384d266457e7a4d5cf85
sbom-static-validation-repository-report.json.zip
279 KB
sha256:9aa697d25ddd41303f0b653bc300ec5a4f554c6477108bbc1d129ada9427221b
sbom-transform-data-service-repository-report.json.zip
279 KB
sha256:4ae5b6897590106a06163181797c8678eb4b5e9359d73c34972a0af64d4f6ac8
sbom-update-blocked-flag-repository-report.json.zip
279 KB
sha256:b7d498531891177de8541e9fd4317fd5bd1f1f74b81f2718bbe8dbccb1e13822
sbom-update-exception-repository-report.json.zip
279 KB
sha256:1c1b50c850a91a65785556ef695826abf448b82f85fa0f04f389190ff3385dbc
sbom-web-repository-report.json.zip
279 KB
sha256:e10310ddcdb4edde766e6c70b7cb1295f6ea38f43560a983c38abfc9bcd87119
sbom-wiremock-repository-report.json.zip
279 KB
sha256:3c342213315b8f2b0f349e2a68d11aeecdffc76e63f80f11a603e55adb4e1c2e
test-coverage-report
322 KB
sha256:ca86e27aa979b9fbd579a8d0944ee5882f8073f2aaee33352ab199b8ed1fa07c
test-results-consolidated
691 KB
sha256:d2d6edbaf73e343f01ae1190ed1a1eeb8f08fe3bb32c6b87b084b3283c25c088
vulnerabilities-audit-writer-repository-report.json.zip
27.3 KB
sha256:c8d3ef4e141385f22034939e1abf8fc858677ac29410506000183a58224c63bc
vulnerabilities-bs-request-audit-data-service-repository-report.json.zip
27.4 KB
sha256:6307c502341d5d9efb8947dec8e572604fe601e367ccd5b02ad7ee2493e8bafa
vulnerabilities-cohort-distribution-data-service-repository-report.json.zip
27.4 KB
sha256:a8411a6d5e9de29e10df7bda71104a44a9e3bb6629a2ee46490491ac00d26aa8
vulnerabilities-create-exception-repository-report.json.zip
27.3 KB
sha256:249c6c6dccd971369a4e5ebf1aec39840df39e7986d786e34b99fb0a383d1dcb
vulnerabilities-db-migration-repository-report.json.zip
27.3 KB
sha256:440a48b737c9c77075e9e3e6d5b11a36457092da21d740def5bf3aaaa1b37fb1
vulnerabilities-delete-participant-repository-report.json.zip
27.3 KB
sha256:7a26fd47f848aef2e2bc6111f0c2424d1f15549273f3ee68e2f885e3b6d785cd
vulnerabilities-distribute-participant-repository-report.json.zip
27.3 KB
sha256:4a4fdce9503b66ea0986689902bb8db2c3f9ca8ffdb9fbeafa8378f786df3030
vulnerabilities-durable-demographic-function-repository-report.json.zip
27.4 KB
sha256:82040bb0a3deb9a0c890470aa5116edb4f23eb42e64b3f56555c7d5246b50c06
vulnerabilities-exception-management-data-service-repository-report.json.zip
27.4 KB
sha256:4a7358584c477f04e0967c53833a8457b4cb21450cb5f5a1a99eaab64cd939a8
vulnerabilities-gene-code-lkp-data-service-repository-report.json.zip
27.4 KB
sha256:8ce9bda4bfe1b151a292016c6f6aac6b8f3844eb993fa25394b7051101f2c82a
vulnerabilities-get-validation-exceptions-repository-report.json.zip
27.3 KB
sha256:15cb9ad57f54be88a0796eda8d3c9987102c1d5533543f4dd8a2add537db06d5
vulnerabilities-higher-risk-referral-reason-lkp-data-service-repository-report.json.zip
27.4 KB
sha256:be78d21c7fcce9f88bdbc185d74f9ba615521d6ebc892a556ba71b59dfa4e5dd
vulnerabilities-lookup-validation-repository-report.json.zip
27.3 KB
sha256:bddbd2c090347a64bbd73e26a67190759c7d669f2bd76228ce871d0d88c55f69
vulnerabilities-manage-caas-subscription-repository-report.json.zip
27.3 KB
sha256:f7777b4089f686739dde52ec1f2fbb25543b93fc66c9f87d5a944d612014cdd1
vulnerabilities-manage-nems-subscription-repository-report.json.zip
27.3 KB
sha256:8a7fc61d5e8adc866f8807a1bde7e6dd1a15d87654de3d18b421c6b8f6af63df
vulnerabilities-manage-participant-repository-report.json.zip
27.3 KB
sha256:f5b0d588231f8ca47c72bec75f80c2151acbf398a3d269459c7bf4ffee81bb12
vulnerabilities-manage-servicenow-participant-repository-report.json.zip
27.4 KB
sha256:663575dc708d0b0dd9f490bb916280c83d49231c567d1038de2e5cedf85ac924
vulnerabilities-nems-mesh-retrieval-repository-report.json.zip
27.3 KB
sha256:a12a29c16add16265fdbdb2aadc24af478683dd2613ebb3b689fc2a503a92a7c
vulnerabilities-nems-subscription-data-service-repository-report.json.zip
27.4 KB
sha256:71f40fb06ac796448be203ad4db201463a67c8741fc960c91b8f37cefb962a18
vulnerabilities-participant-demographic-data-service-repository-report.json.zip
27.4 KB
sha256:ec4896515ed52a909128d2560e2bb88e99b26265aa4e6c8c96edc89b4a7796cc
vulnerabilities-participant-management-data-service-repository-report.json.zip
27.4 KB
sha256:09e989387849758c884c98fd3b0a6947d0d426a5281a3b7bc7706cbc0fd8cc85
vulnerabilities-process-nems-update-repository-report.json.zip
27.3 KB
sha256:f7fffccfcdd0ad92c60e2bb36a9793cdacd73d83af972c1296f84ae91434581d
vulnerabilities-receive-caas-file-repository-report.json.zip
27.3 KB
sha256:38331afddd89a17727b6417cab1e9dcda1487cec4921d393405d4377d007b67a
vulnerabilities-reference-data-service-repository-report.json.zip
27.3 KB
sha256:ba881cd88df648be5bf56eef5811e49aaa584d7998db9d46ccbff28e153ce403
vulnerabilities-remove-dummy-gp-code-repository-report.json.zip
27.3 KB
sha256:a14f3acf38ea79ecb02c283a1b43af18223c4fd45015fc3d76ab09f23286fc4e
vulnerabilities-remove-validation-exception-data-repository-report.json.zip
27.4 KB
sha256:7d44ff7b304c028a3b31fca09c7a46a351f5033ad8188bd6646db413988d31ad
vulnerabilities-retrieve-cohort-distribution-data-repository-report.json.zip
27.4 KB
sha256:4f73345dfe29b8845790a75bb42fd0fb1e5a933c67c3512727f53439fd761009
vulnerabilities-retrieve-cohort-request-audit-repository-report.json.zip
27.3 KB
sha256:17526bc55806cfe5757262e466d260d66518fad7880f7816e045ad3a77f42d0d
vulnerabilities-retrieve-mesh-file-repository-report.json.zip
27.3 KB
sha256:75b9acb9e8778b8ea625c59e9d1ad16123a9e7e8107038923152e60bb5d3f0c1
vulnerabilities-retrieve-pds-demographic-repository-report.json.zip
27.3 KB
sha256:eef1cef9730e57cd9a5a6b81c63e17ba4f13d54ceba74c53cf27826af4c96105
vulnerabilities-screening-lkp-data-service-repository-report.json.zip
27.4 KB
sha256:c08252a9704b96b97dcde79dc2057ff520e9fcca510dfa9bcdf7eaf4520005e3
vulnerabilities-servicenow-cases-data-service-repository-report.json.zip
27.3 KB
sha256:af5bddd5cc9503ab1a0ca0d372ec058fdcc9fb380e6e8cf1085f88049c2b5676
vulnerabilities-servicenow-cohort-lookup-repository-report.json.zip
27.3 KB
sha256:9df95b1ec40029ce40c0f58114ded0c3ff34158cf51170d815a768e56bb0fcd5
vulnerabilities-servicenow-message-handler-repository-report.json.zip
27.3 KB
sha256:33de3fcc7e688272359504d4603057208e5753da6f52caf56b03c91418877105
vulnerabilities-static-validation-repository-report.json.zip
27.3 KB
sha256:edb81cf44e7b80473b77e70113fd6ba75752108f1e28eaaf4616bd14400b20e1
vulnerabilities-transform-data-service-repository-report.json.zip
27.3 KB
sha256:e4485023ec8e2a0e74962b9a3404e1c13302fd0589ad8806e19eacd7302d043d
vulnerabilities-update-blocked-flag-repository-report.json.zip
27.3 KB
sha256:2373f745ea5babfcccb5435648c8e5a58e89d2bd1516a3355af2125c3ea6a590
vulnerabilities-update-exception-repository-report.json.zip
27.3 KB
sha256:1553d1b7ac74ba7a4bb7d28efd34eb5b61add8785f3a5d3b209d3bde4703f979
vulnerabilities-web-repository-report.json.zip
27.3 KB
sha256:83e291a19437d6c30448d296e8c59d364247e6682e31e3f9038b0d0f1cf2831a
vulnerabilities-wiremock-repository-report.json.zip
27.3 KB
sha256:35ed7c2a009202610b76640988b02bd6e4d1b7d20a2d5041482ca6a56b419b3d