Skip to content

feat: wire-up dummy gp code changes #15482

feat: wire-up dummy gp code changes

feat: wire-up dummy gp code changes #15482

Triggered via pull request April 30, 2026 10:09
Status Success
Total duration 17m 44s
Artifacts 125

cicd-1-pull-request.yaml

on: pull_request
Set CI/CD metadata
6s
Set CI/CD metadata
Validate PR title
6s
Validate PR title
Commit stage  /  Scan secrets
17s
Commit stage / Scan secrets
Commit stage  /  Check file format
11s
Commit stage / Check file format
Commit stage  /  Check Markdown format
6s
Commit stage / Check Markdown format
Commit stage  /  Check English usage
12s
Commit stage / Check English usage
Commit stage  /  Lint Terraform
7s
Commit stage / Lint Terraform
Commit stage  /  Count lines of code
6s
Commit stage / Count lines of code
Test stage  /  Check for consolidated test project
5s
Test stage / Check for consolidated test project
Test stage  /  Run consolidated tests
2m 56s
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
7m 6s
Analysis stage / Perform static analysis
Image build stage  /  get-functions
9s
Image build stage / get-functions
Image build stage  /  build-base-images
2m 2s
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#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/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.
Analysis stage / Perform static analysis: 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.
Analysis stage / Perform static analysis: 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.
Analysis stage / Perform static analysis: 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.
Analysis stage / Perform static analysis: 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.
Analysis stage / Perform static analysis: 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.
Analysis stage / Perform static analysis: 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.
Analysis stage / Perform static analysis: 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.
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 (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 (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 (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 (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 (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 (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 (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 (web)
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 (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 (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 (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 (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 (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 (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 (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 (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-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 (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 (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 (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 (servicenow-cases-data-service)
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 (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 (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 (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 (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 (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 / 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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 / 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-pr1895.zip
10.9 MB
sha256:f5e19cf49143c573de15ef8ad3b16f07a168a11ad15688bb9be5359b276c0458
aggregated-vulnerabilities-repository-report-pr1895.zip
558 KB
sha256:774d1ba50033495364e14130f87e7cd30ffa62bbf785a9ccf13283b93fe4846d
cohort-manager-audit-writer-vulnerabilities-summary.txt
2.26 KB
sha256:f8e49ae453e72827449f816c1230252bf61e6c5455b6a889b271de50ffc789c9
cohort-manager-bs-request-audit-data-service-vulnerabilities-summary.txt
2.31 KB
sha256:d722cac4c24c2c689541eee5724af3856b228bb7a5c2ddc627395888f7dd5d71
cohort-manager-cohort-distribution-data-service-vulnerabilities-summary.txt
2.31 KB
sha256:d4f164b430d09a29fd33b991a8a776b6e0d711650d0673b1594a1d6504c118cf
cohort-manager-create-exception-vulnerabilities-summary.txt
2.27 KB
sha256:620f9713c875ce3aec30af0acd90cc2abecda9de9e70a9256aef0310edf845f2
cohort-manager-db-migration-vulnerabilities-summary.txt
1.73 KB
sha256:351e008f937c04215ff47ab442e1ae8d240615a93ddf9052a570a591e758ca3f
cohort-manager-delete-participant-vulnerabilities-summary.txt
2.28 KB
sha256:3131e270732b24811c638232cfe8b7c42a027c39daa8495e2c4d44e689f95319
cohort-manager-distribute-participant-vulnerabilities-summary.txt
2.29 KB
sha256:99ec8da49f29854eeef2b76ecb3d673ffdc45f72ea0019fa8c90cc36fb1124da
cohort-manager-durable-demographic-function-vulnerabilities-summary.txt
2.31 KB
sha256:b63c2ae46448b8fb48447ccacef6098fda0f5822dbd315698688a9e2614cc054
cohort-manager-exception-management-data-service-vulnerabilities-summary.txt
2.31 KB
sha256:c1efad1f91f077064a0cf34ad1aa50830ad123155e94ab074a1c1ebb16839392
cohort-manager-gene-code-lkp-data-service-vulnerabilities-summary.txt
2.3 KB
sha256:7829ec4d71b56f00472137e93a7a46bbcfeb6cb557d78d819cefbb010cfa5694
cohort-manager-get-validation-exceptions-vulnerabilities-summary.txt
2.29 KB
sha256:8ec924f6b496c8dcf9aef5386d0e4867eee2bfe7ae3fe9420fae9e2ffa72d66c
cohort-manager-higher-risk-referral-reason-lkp-data-service-vulnerabilities-summary.txt
2.35 KB
sha256:0b21936994c598d6ad2e1a2d2b025cf8d96a7950d8ff6467190d6cf9819d3212
cohort-manager-lookup-validation-vulnerabilities-summary.txt
2.27 KB
sha256:2db5b0535ec94fbbdd6ef471dfffe12ba866bab164c83a3d2f5dac3cd8341c57
cohort-manager-manage-caas-subscription-vulnerabilities-summary.txt
2.29 KB
sha256:d728b4707cd6eeedba777cfab663651767f12846fee9eee2319b7054b3972306
cohort-manager-manage-nems-subscription-vulnerabilities-summary.txt
2.29 KB
sha256:1e9881ab90700ce7463298bae0f346014ba30559a2dfa36b09977cf3779782a6
cohort-manager-manage-participant-vulnerabilities-summary.txt
2.27 KB
sha256:dc575eee882411075882e2de4b4b38aa613f2c951829ffe2bf588222ea7d8b6f
cohort-manager-manage-servicenow-participant-vulnerabilities-summary.txt
2.3 KB
sha256:d1d95ac83bb99aa5146b9d7444dd1f468cde248ccccb33a699d87d2fef5b78e9
cohort-manager-nems-mesh-retrieval-vulnerabilities-summary.txt
2.28 KB
sha256:d0cb8c6fac06386bed8aa4600373928da926913c914e22e7e3964e9dd67fdbe2
cohort-manager-nems-subscription-data-service-vulnerabilities-summary.txt
2.31 KB
sha256:48ff63ee68c23138cabfe6a024f8dabe3d5e2379d00eca0b8ff3c0f5da088c78
cohort-manager-participant-demographic-data-service-vulnerabilities-summary.txt
2.32 KB
sha256:5b703f7333df87c80c10c816bfd0a27def0a7a11eb62f2b0cf9f187407e032cf
cohort-manager-participant-management-data-service-vulnerabilities-summary.txt
2.32 KB
sha256:6de6cd51af01cc7bf3fed1054a7e9260b5822a5cfc9affb55e37583203011d53
cohort-manager-process-nems-update-vulnerabilities-summary.txt
2.28 KB
sha256:3419aca659007955a3e75ab1f44b51a2ba32295e5cb3ea4c570548be3877e74c
cohort-manager-receive-caas-file-vulnerabilities-summary.txt
2.27 KB
sha256:8b314edf09dab10f309efaf09ffca414b7c2c9eebc5d08efa44175f1799655e9
cohort-manager-reference-data-service-vulnerabilities-summary.txt
2.29 KB
sha256:28fc6b9ab8592673ee601f15613a0c3fa458666fae3b515e8fa7db3694a97cff
cohort-manager-remove-dummy-gp-code-vulnerabilities-summary.txt
2.28 KB
sha256:15740d32732a46e48bc6c78ef74946515ce81a4fedeebeccdd75033a5f4c91cf
cohort-manager-remove-validation-exception-data-vulnerabilities-summary.txt
2.31 KB
sha256:4f41851cf9e172efe5c74579728d3edaf33bbd7bea1751c8d978d0e0ea0df3f1
cohort-manager-retrieve-cohort-distribution-data-vulnerabilities-summary.txt
2.31 KB
sha256:6bf5bb5a70fa4e08fbbd3787eabcd01d87921f47ebdd99affa716a90779988ce
cohort-manager-retrieve-cohort-request-audit-vulnerabilities-summary.txt
2.3 KB
sha256:44083b5bed9925e780ab044d300231e40136336cec0f7d5cc636e7613e826273
cohort-manager-retrieve-mesh-file-vulnerabilities-summary.txt
2.28 KB
sha256:100e745138503278b7e73f8d1652d36dd2a232d6aa08191402b926d8c5de4cdf
cohort-manager-retrieve-pds-demographic-vulnerabilities-summary.txt
2.29 KB
sha256:c494747f4d660fdedb9f150507218237fbf1ef8c75ac166012340b9b65057f5e
cohort-manager-screening-lkp-data-service-vulnerabilities-summary.txt
2.3 KB
sha256:92b2dfd37864e16928d805603b24aefbd41f3a47d9499befb4063815085bae7c
cohort-manager-servicenow-cases-data-service-vulnerabilities-summary.txt
2.3 KB
sha256:1699e4702b09f1bc0e96640adc3532091ef167099f895ccf2ffd8bf1d9cb9f4e
cohort-manager-servicenow-cohort-lookup-vulnerabilities-summary.txt
2.29 KB
sha256:3cdcdbc5937fe608e96978f025d087f14711d43d6e35916e181c112d3844b7ca
cohort-manager-servicenow-message-handler-vulnerabilities-summary.txt
2.3 KB
sha256:0cf2d3764f181687dbe8d28078e3234c781afac417d508bc84e220887a1e54f8
cohort-manager-static-validation-vulnerabilities-summary.txt
2.27 KB
sha256:a9b6d8f91c0aa7932473e6e0f8a1353a31f53f43974f3de50607aba34c2f8237
cohort-manager-transform-data-service-vulnerabilities-summary.txt
2.29 KB
sha256:47efee1f462a01ce7ed2cc7c1f6b006041ea0cda105da7ff1a8c399ee331b304
cohort-manager-update-blocked-flag-vulnerabilities-summary.txt
2.28 KB
sha256:0d6bfe05ce022a9517b3a8982a37a61c1b6601bcce90e170224acf58369207a5
cohort-manager-update-exception-vulnerabilities-summary.txt
2.27 KB
sha256:50f8af470fc77da1e63ca9fcfa0fca623049f8fe9df43c89d7126da223cde2a6
cohort-manager-web-vulnerabilities-summary.txt
511 Bytes
sha256:20ae44ca3844f479d68dd0dd036be88a4cb3b10785420235b3a0510d1a5e1e02
cohort-manager-wiremock-vulnerabilities-summary.txt
1.59 KB
sha256:9617baa0eae50bcc711e1d6ec30153224b2003b2bcea17dbe3a84086e433305e
lines-of-code-report.json.zip
992 Bytes
sha256:02e87d2d511d40ed390cb5bc3682b049e3b5550163d1a2c4182f067e75362b1c
sbom-audit-writer-repository-report.json.zip
280 KB
sha256:04706446c1a2de73b84a99e8f12968237711fe0df6cf6f61c557c95c4a0441a8
sbom-bs-request-audit-data-service-repository-report.json.zip
280 KB
sha256:9cdd670f16ed046665e52155d21b2d935aaa306c805fcca5985eb3699a3baa88
sbom-cohort-distribution-data-service-repository-report.json.zip
280 KB
sha256:af636bdf28eb0089eff8e4d8ed34022f539ae15da8c06897b9c79ffe7151ec7d
sbom-create-exception-repository-report.json.zip
280 KB
sha256:7df113f5477aef2acbeeba87193ec73377283511301f76b18ca8718e07dd6256
sbom-db-migration-repository-report.json.zip
280 KB
sha256:5183b1eb3db2da93961e48b26deefc7746afabe349550ce1de9ddafe31412071
sbom-delete-participant-repository-report.json.zip
280 KB
sha256:b9ddda33f475fd2f25a8d9fce8758dc92ab625a30c70e359412ab60cb05de414
sbom-distribute-participant-repository-report.json.zip
280 KB
sha256:54e0028e9428279d481170dba22fd6c6d9533b6a16d5d552a08fe615f2693f8a
sbom-durable-demographic-function-repository-report.json.zip
280 KB
sha256:8851f48d82604efdc74f9f451a96bfac5a54cd5ef138b020953b55b204ee56d9
sbom-exception-management-data-service-repository-report.json.zip
280 KB
sha256:10e9b67917d0f2c1b09cb13d075eb6f80684680598a2acba5e5c1baad3364fee
sbom-gene-code-lkp-data-service-repository-report.json.zip
280 KB
sha256:a0c64a2abae9db49954b79241744e6356424ff5789a573ead5fb158697f89207
sbom-get-validation-exceptions-repository-report.json.zip
280 KB
sha256:3f7224c675e1789c627dc5045babcf5e79e1da9e771bc7e4cf2c677e56675c7c
sbom-higher-risk-referral-reason-lkp-data-service-repository-report.json.zip
280 KB
sha256:caf37f543cdfb7cb10ab6c4ab6e00efb8d9405774a9f9b2bdc09a08b8401ea43
sbom-lookup-validation-repository-report.json.zip
280 KB
sha256:e6e739b617fbd3cbc1995df25a676ea59fcf801713d9ced52d0346f4f9aa7809
sbom-manage-caas-subscription-repository-report.json.zip
280 KB
sha256:ff84f85dc0d8d5c7696ce2269ef2a705512e76f39a3fa04cff208a7a36cba7d3
sbom-manage-nems-subscription-repository-report.json.zip
280 KB
sha256:df19811289a0feaa8cddaade03c5c088edff76483e0029527f7d9ae9ad386264
sbom-manage-participant-repository-report.json.zip
280 KB
sha256:1dfe094493ff22822940fa4f6a41f1f8aa8962ee8b7f1b222545424c9e347f31
sbom-manage-servicenow-participant-repository-report.json.zip
280 KB
sha256:2588c17391014cac10af91c2e703ac9191300b24c1bc18a53a5cc1a81d53872f
sbom-nems-mesh-retrieval-repository-report.json.zip
280 KB
sha256:db4615caa6c7af4e66725db99caed77d4fb5dd20c755a25668364f43e3132e85
sbom-nems-subscription-data-service-repository-report.json.zip
280 KB
sha256:63677281c16c8481df44f27c386595924e8f71022a771f7405d3bf40f2b12eae
sbom-participant-demographic-data-service-repository-report.json.zip
280 KB
sha256:cfabddbb2ae1b706cfbb684a484ddd5923155531d7be5726f7793127922315b7
sbom-participant-management-data-service-repository-report.json.zip
280 KB
sha256:1615527772a13c996ef71f586524c938ff463aa29d0958d737c8df71c153f16a
sbom-process-nems-update-repository-report.json.zip
280 KB
sha256:dde6dbc160fda827868cc4c701c59cf6c99705b72abdd0a41f0333d5c378c81c
sbom-receive-caas-file-repository-report.json.zip
280 KB
sha256:c0ed797f79171db5fa6676d4cfe8c9be591109f68a0d653adb775a013800e383
sbom-reference-data-service-repository-report.json.zip
280 KB
sha256:7515ea8f7bb3f07b84c27ea3d9d5ae47fb8816bc25aafc022fb80605a2404cfa
sbom-remove-dummy-gp-code-repository-report.json.zip
280 KB
sha256:45e28cb28a16ef56745e4c7ddcfa2460ef6ea85afc8f4102595c62e3f8572e3f
sbom-remove-validation-exception-data-repository-report.json.zip
280 KB
sha256:8ab7aa887c367b775d009245c35de29ba9b13e423122f719537e087e80933d72
sbom-retrieve-cohort-distribution-data-repository-report.json.zip
280 KB
sha256:681fce90673a91564b982a4b3d27b8277b84d936239e85d04855663c75d3f119
sbom-retrieve-cohort-request-audit-repository-report.json.zip
280 KB
sha256:b1d1bd025f43e35288ddc024e0d52a573a654b5904192e6862410c2a1f4e7bd5
sbom-retrieve-mesh-file-repository-report.json.zip
280 KB
sha256:5bfce44e6e49f3f75922ef19934d7b2d712b8535fcc29a1c48d199073c64a2f0
sbom-retrieve-pds-demographic-repository-report.json.zip
280 KB
sha256:d8dd5a087351e07ceee2e3a4f09b9c4897372a2174184e6c4ca42dd3f2600113
sbom-screening-lkp-data-service-repository-report.json.zip
280 KB
sha256:834181f13b612db1ad5f26d5c9da70de9122230e7deef244cc5484a99b8c674a
sbom-servicenow-cases-data-service-repository-report.json.zip
280 KB
sha256:6d9eaea60c7835dc61e755ac76606b045839d9d2fde01bed96892f3827036141
sbom-servicenow-cohort-lookup-repository-report.json.zip
280 KB
sha256:c71903c84cbba3ad7a4f86202fc931c7e61e504259deaef72e51ce15ff94b1b8
sbom-servicenow-message-handler-repository-report.json.zip
280 KB
sha256:0ec728c989981f1ef248a78c6057344c575dbbaa3b61c55f697dcc93e259aff4
sbom-static-validation-repository-report.json.zip
280 KB
sha256:53a3047f0e836177ad63b7e66dff419e6d9f3c0284ee0f0074172bf1b102449f
sbom-transform-data-service-repository-report.json.zip
280 KB
sha256:4ea54b1bbc701856b46447416b187e47f0dbe83b36ca6a16455ff3e12ef31d71
sbom-update-blocked-flag-repository-report.json.zip
280 KB
sha256:2f7c8853b670a6f482e31e70e6d87decb889f8519a0cf203817200b257dfce73
sbom-update-exception-repository-report.json.zip
280 KB
sha256:014ab36720e7ffae1f8aa7892502c4402c9cd5bb0345af9d5137d03defd57884
sbom-web-repository-report.json.zip
280 KB
sha256:72c7a8cd46d7299a90d3cda447a205ae0541bdd76fdbae95e443e9cc6cf91c1c
sbom-wiremock-repository-report.json.zip
280 KB
sha256:3bcb874844beda9a74bbb3549cc8457075a07b99020b310d2da48fec1b73fac3
test-coverage-report
320 KB
sha256:a700c7109909bef9191d127cef7915492ac9278594552e546af0381b6f0cd10b
test-results-consolidated
687 KB
sha256:ab2875285c4807d0cfa7c36db81541488202d6adbcf4b5bb4ec74d867d20e05e
vulnerabilities-audit-writer-repository-report.json.zip
27.3 KB
sha256:41e9372e295a814311e1b5957ce1493588d6b00074a39d5a899ad50b9afd4d7f
vulnerabilities-bs-request-audit-data-service-repository-report.json.zip
27.4 KB
sha256:4dd6d23d908b294d6ab052f867080e82661b91aec06d4b6a814c7a3f8663eb8f
vulnerabilities-cohort-distribution-data-service-repository-report.json.zip
27.4 KB
sha256:45ac5b19051e263b2d0112094b234322b78e5dc501e1d4c776a191036a90b98a
vulnerabilities-create-exception-repository-report.json.zip
27.3 KB
sha256:a6052eca3b0010d87a4080e8d21109cdbb4fe31aaeda952eeebe7dbc2b594af2
vulnerabilities-db-migration-repository-report.json.zip
27.3 KB
sha256:8fce3d48418c2309df27eb7a3a9d81ea6186307267bab655b06d492ee1f472a1
vulnerabilities-delete-participant-repository-report.json.zip
27.3 KB
sha256:35e00d32547e0ac37ecc840a0a88cddd21479d52bfec4507e60005fc717a83d2
vulnerabilities-distribute-participant-repository-report.json.zip
27.3 KB
sha256:813bd8055b609e41e933219c3e00640ac923fadd314d440803cc9536a6ba6828
vulnerabilities-durable-demographic-function-repository-report.json.zip
27.4 KB
sha256:ae307bcfd80ac9b007a74dec5ad860763596b1f1e6f9b4b48b69768ae4320242
vulnerabilities-exception-management-data-service-repository-report.json.zip
27.4 KB
sha256:1cbe318d0d2dedecd2837e56e9720f087ddc90ebff34399ff21ec70a05498af3
vulnerabilities-gene-code-lkp-data-service-repository-report.json.zip
27.3 KB
sha256:5d42d5e091b7386f186cc7aadf382fd33b0835fddad7e93f424a61223cff57ce
vulnerabilities-get-validation-exceptions-repository-report.json.zip
27.3 KB
sha256:fd2749ec655d633215195448c210b4f247f7919d52fcb7d4252b0ffe4c708ea1
vulnerabilities-higher-risk-referral-reason-lkp-data-service-repository-report.json.zip
27.4 KB
sha256:cc4be34390730e4bb6e093a3a8676616d1f9e00d4fc9e01f4de8b370d0a8ad1e
vulnerabilities-lookup-validation-repository-report.json.zip
27.3 KB
sha256:0d97f559eb15fd63b4fff40806343a41ea56b435478a69b31d51fe3cf776ba5b
vulnerabilities-manage-caas-subscription-repository-report.json.zip
27.4 KB
sha256:3445aaf4886757c3145fcff2b25d7b8ec36d0af25aba5f750945b5def6a68d76
vulnerabilities-manage-nems-subscription-repository-report.json.zip
27.3 KB
sha256:1bb6e8b032d373374776dd611cc72e406303a9a71726e471d0b2e369c3005dff
vulnerabilities-manage-participant-repository-report.json.zip
27.3 KB
sha256:77e6262b60e1f5647727389ce1d41b3715d6b9f548ca204bb0fb78a507f5c872
vulnerabilities-manage-servicenow-participant-repository-report.json.zip
27.4 KB
sha256:b378b9adcdc9da34da8503adadc12f919ca2389801f638b1e2e1671131351aa6
vulnerabilities-nems-mesh-retrieval-repository-report.json.zip
27.3 KB
sha256:161e0181dbce4a11c6e1321a5f38713b455028c30c0d329f5789997055c69bcc
vulnerabilities-nems-subscription-data-service-repository-report.json.zip
27.4 KB
sha256:0b1ef6942144213531be88f515a25676e418a9336eebbba277001603e15585f3
vulnerabilities-participant-demographic-data-service-repository-report.json.zip
27.4 KB
sha256:612051fe9da465aef2d0ce4c8ea4d76574b9f5f2ab06379cfd4518057bc55a78
vulnerabilities-participant-management-data-service-repository-report.json.zip
27.4 KB
sha256:b829a990aad05ca178eebff3e9eb3bdfe617319dc18c85b7ab0393661c4ca6aa
vulnerabilities-process-nems-update-repository-report.json.zip
27.3 KB
sha256:882d2226025658380968daec824e66961b9d8556ecf72718733600aafa8481d1
vulnerabilities-receive-caas-file-repository-report.json.zip
27.3 KB
sha256:766ecedef294e40af3c6007a658fa63a69c9e67b48bc103de5540022ba344bf6
vulnerabilities-reference-data-service-repository-report.json.zip
27.3 KB
sha256:e09cd62c6a6735d84c43e153a10e831923e7ee26462e4cca738fcd6efb82704a
vulnerabilities-remove-dummy-gp-code-repository-report.json.zip
27.3 KB
sha256:60513e7e502c1692544d9667a5c014c82cda876bc624e33e55d060a2d66f1083
vulnerabilities-remove-validation-exception-data-repository-report.json.zip
27.4 KB
sha256:726b20376ed65bec28c395774e0710908b13dc053bd637a735dbe2d6c5669d58
vulnerabilities-retrieve-cohort-distribution-data-repository-report.json.zip
27.4 KB
sha256:8bf40f6c235efc8bdb208b4aa27f27dd84ce2915aa45246e1a9150350b947a4b
vulnerabilities-retrieve-cohort-request-audit-repository-report.json.zip
27.4 KB
sha256:e2e92f69611f2b9af237fe5adcdee92babc0e588f05b372b9899b82190ee430f
vulnerabilities-retrieve-mesh-file-repository-report.json.zip
27.3 KB
sha256:19a839a59385eb075600f986e60b97a970509e55cd5d4425f70b02d8573a5231
vulnerabilities-retrieve-pds-demographic-repository-report.json.zip
27.3 KB
sha256:c975ab1b8fc6af5e6056e0a8bd2a8b11880cbc5c7639bcaec3f3d8a6a3f81460
vulnerabilities-screening-lkp-data-service-repository-report.json.zip
27.3 KB
sha256:7857de0f1db45ebf64d88357b86235e8eddaa67fd1338360a07c6e3e8bb11b9b
vulnerabilities-servicenow-cases-data-service-repository-report.json.zip
27.4 KB
sha256:a671162948583138cc5c7912b1a161e96461ca0f21f79ba10afdb6190c4386fb
vulnerabilities-servicenow-cohort-lookup-repository-report.json.zip
27.3 KB
sha256:16ef609b3b3d8e277f10c1a68a33059fbfaccc6ce3c34fe107b1a510ad6e73f0
vulnerabilities-servicenow-message-handler-repository-report.json.zip
27.4 KB
sha256:4ab1678e578f7c883b6dbdcb8a89b321dc91ce21650e31a14d9301b31fbdd5fe
vulnerabilities-static-validation-repository-report.json.zip
27.3 KB
sha256:e9605b1b8f063295af48c49acb60b9ffadadcdd3bb9b0d33bbe4cba1025182de
vulnerabilities-transform-data-service-repository-report.json.zip
27.3 KB
sha256:f3dddf3476b85b2ee7b1e035bcad8c4b49da1e6d31c9173ac80770b94f1d9b53
vulnerabilities-update-blocked-flag-repository-report.json.zip
27.3 KB
sha256:94a09d9e6e13c4f1c41bafb840a1b0c6b8f1ee0084171cf166673ca4fa85788b
vulnerabilities-update-exception-repository-report.json.zip
27.3 KB
sha256:09c277b989bcd73e790ae78c87edf7a065a45def332c9b0ba64a8242cb39d565
vulnerabilities-web-repository-report.json.zip
27.3 KB
sha256:8f9c27bfa37472303d9677d025cb3bc43673938931979cb2ff5dc630d04543b2
vulnerabilities-wiremock-repository-report.json.zip
27.3 KB
sha256:80e5a30c7ad9aa5353413b08a88c16d67d016ad049e11e6bb0eec22add978b99