Skip to content

feat: AuditWriter Health check #15494

feat: AuditWriter Health check

feat: AuditWriter Health check #15494

Triggered via pull request April 30, 2026 16:36
Status Success
Total duration 15m 26s
Artifacts 125

cicd-1-pull-request.yaml

on: pull_request
Set CI/CD metadata
10s
Set CI/CD metadata
Validate PR title
6s
Validate PR title
Commit stage  /  Scan secrets
14s
Commit stage / Scan secrets
Commit stage  /  Check file format
6s
Commit stage / Check file format
Commit stage  /  Check Markdown format
6s
Commit stage / Check Markdown format
Commit stage  /  Check English usage
20s
Commit stage / Check English usage
Commit stage  /  Lint Terraform
9s
Commit stage / Lint Terraform
Commit stage  /  Count lines of code
9s
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
3m 9s
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
20s
Test stage / Aggregate results and report
Analysis stage  /  Perform static analysis
7m 2s
Analysis stage / Perform static analysis
Image build stage  /  get-functions
9s
Image build stage / get-functions
Image build stage  /  build-base-images
15s
Image build stage / build-base-images
Matrix: Image build stage / build-and-push
Image build stage  /  aggregate-json
8s
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#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#L7
Non-nullable property 'FromMailbox' 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/MessageMetaData.cs#L6
Non-nullable property 'ToMailbox' 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/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/Response/OperationService/HandshakeResponse.cs#L7
Non-nullable property 'MailboxId' 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/InboxService/HeadMessageResponse.cs#L5
Non-nullable property 'MessageMetaData' 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/InboxService/GetChunkedMessageResponse.cs#L6
Non-nullable property 'MessageMetaData' 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/InboxService/GetChunkedMessageResponse.cs#L5
Non-nullable property 'FileAttachments' 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/InboxService/CheckInboxResponse.cs#L7
Non-nullable property 'Messages' 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/InboxService/AcknowledgeMessageResponse.cs#L8
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/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.
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 (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 (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 (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 (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-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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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-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 (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 (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 (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 (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 (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 / 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-pr1899.zip
10.9 MB
sha256:23861363021651f38c86213457bde2ea2288479d3f8bec810f5994b7ce2198d1
aggregated-vulnerabilities-repository-report-pr1899.zip
544 KB
sha256:030a9102b55ccf9f14a92488cda7b0ffc2b7c101466c88e44152ae169268971a
cohort-manager-audit-writer-vulnerabilities-summary.txt
2.26 KB
sha256:ce7ff3873dd4f8f2c74a13cc622b302bb5a91c7bbb01aac0f8b268f1b1e584b7
cohort-manager-bs-request-audit-data-service-vulnerabilities-summary.txt
2.31 KB
sha256:9cda94187f3571169b0c85b7e676dc2da4615acbce147d400aae86cca111c143
cohort-manager-cohort-distribution-data-service-vulnerabilities-summary.txt
2.31 KB
sha256:869ff9d356c59d6d539d7099d77df37a61b5bdb69a2fd7907cf6df6e23ffe405
cohort-manager-create-exception-vulnerabilities-summary.txt
2.27 KB
sha256:c275fcc0612c0c851b69f9000ccd3ca3ca7eff8f70a500fb1cdbbeb46d1e9e7c
cohort-manager-db-migration-vulnerabilities-summary.txt
1.73 KB
sha256:0f44232bc5ed286a66a8d43dd51a5f7e812689c049de5b03157af781c7ab9da9
cohort-manager-delete-participant-vulnerabilities-summary.txt
2.28 KB
sha256:f1a890f9f0da8816b567f261f7dbf467be9a393c931d0a33315ee011f0606f80
cohort-manager-distribute-participant-vulnerabilities-summary.txt
2.29 KB
sha256:4d1d212d16e578610db7f791d5deaffbf947b5f5deeadd963e8885dbd12b0dc1
cohort-manager-durable-demographic-function-vulnerabilities-summary.txt
2.31 KB
sha256:7f255df4a184ae9bc05e79bc1d32e547289c33809316d9605654f7fa0e73bb34
cohort-manager-exception-management-data-service-vulnerabilities-summary.txt
2.31 KB
sha256:e4722a5c7a8eb00e487b56a5c1f9d09a4355323b038e93bc99dcce9150804f11
cohort-manager-gene-code-lkp-data-service-vulnerabilities-summary.txt
2.3 KB
sha256:bb25a8468f494b7572a092bf92f0aee57cd0f94688cf8390c013f0680d752153
cohort-manager-get-validation-exceptions-vulnerabilities-summary.txt
2.29 KB
sha256:83150fb26a16418a1e6eb73e286b2434f9e5cb442e09dbecbd1651d5720bc5d1
cohort-manager-higher-risk-referral-reason-lkp-data-service-vulnerabilities-summary.txt
2.35 KB
sha256:2246b81cf934c75dd507178353d54d6d4c3c3a4505d2d31c9947203478bd994a
cohort-manager-lookup-validation-vulnerabilities-summary.txt
2.27 KB
sha256:54713aae39b0de53ea6d97594305510fa5a36b191509eb2c0d900b7caf0540b0
cohort-manager-manage-caas-subscription-vulnerabilities-summary.txt
2.29 KB
sha256:0de523e1cb1cc2f7705a4ec6a11f86e86247eecbcef2c0a5652a1d307071d14a
cohort-manager-manage-nems-subscription-vulnerabilities-summary.txt
2.29 KB
sha256:21c281606280267f9356235db92fb65aba195eee2b06d32a9ceeebcddaf8e5b0
cohort-manager-manage-participant-vulnerabilities-summary.txt
2.27 KB
sha256:edf11f98b5fd0f96291fc2fe14339243561abf41146748dec533cc744597cf88
cohort-manager-manage-servicenow-participant-vulnerabilities-summary.txt
2.3 KB
sha256:2c8d10023a1c2edee827a9f4ecc7890a27097388bc4454deabda1a86503859c3
cohort-manager-nems-mesh-retrieval-vulnerabilities-summary.txt
2.28 KB
sha256:6917cfe70cea6ae8831ab584a577f7818d97355bdfb5158eed37ad9286eb7b95
cohort-manager-nems-subscription-data-service-vulnerabilities-summary.txt
2.31 KB
sha256:98eef952585443742d0b2321cbffe41971f935f5eb68df59c4b73e8daa529b8d
cohort-manager-participant-demographic-data-service-vulnerabilities-summary.txt
2.32 KB
sha256:033af85b9daadbb45dc5260fa913e55d56e7e804cc9ba5e5ab9675c69fce2c41
cohort-manager-participant-management-data-service-vulnerabilities-summary.txt
2.32 KB
sha256:0d1c64284b608bf5b428a7b790213b6e868c795af3003004823e87aa93001dfc
cohort-manager-process-nems-update-vulnerabilities-summary.txt
2.28 KB
sha256:b848a3970e0358ac14142cb9eef995a3a2ec42f798a962729de598861c82da53
cohort-manager-receive-caas-file-vulnerabilities-summary.txt
2.27 KB
sha256:dddf675baec9bb55109b7a33411cf8cc044343d6d221d1b5dfbcf4e37ba2d855
cohort-manager-reference-data-service-vulnerabilities-summary.txt
2.29 KB
sha256:32a1beb90ca57e84524678f0b9de2eb9fe8cb47f29f807e1b20c45ea075cb833
cohort-manager-remove-dummy-gp-code-vulnerabilities-summary.txt
2.28 KB
sha256:eb3244535352814e50761fb89e35c89254294b5680d4eac83b34b2cdd4e192f9
cohort-manager-remove-validation-exception-data-vulnerabilities-summary.txt
2.31 KB
sha256:a227c8b9e6a4e85213bda08942afc9567d7066828a8e4d61b487de027b737887
cohort-manager-retrieve-cohort-distribution-data-vulnerabilities-summary.txt
2.31 KB
sha256:4de2954434561472e2f422f8a06b0d06c4b53120877e912a2ecdd0f16f854494
cohort-manager-retrieve-cohort-request-audit-vulnerabilities-summary.txt
2.3 KB
sha256:f4d87c70b2cb175c5a785950694765f1cde099f41558b64df37f6fb52dbf755c
cohort-manager-retrieve-mesh-file-vulnerabilities-summary.txt
2.28 KB
sha256:e1ed5031936447c7b2b4652d87e863d8e5c59d3bef62aa1389c02c9b51bdbffb
cohort-manager-retrieve-pds-demographic-vulnerabilities-summary.txt
2.29 KB
sha256:56ed3b0095999e65c4de53bd57a10f1fddb30bcd588f66d686db77b60d2a9d5f
cohort-manager-screening-lkp-data-service-vulnerabilities-summary.txt
2.3 KB
sha256:daf43563f2330ae3852f9566e6edea84323c638452ad6238d6f72a70ab519f71
cohort-manager-servicenow-cases-data-service-vulnerabilities-summary.txt
2.3 KB
sha256:c84f08daf2b4c3258d02ea5344e9be39406afb77752ae5284864ccace678de28
cohort-manager-servicenow-cohort-lookup-vulnerabilities-summary.txt
2.29 KB
sha256:071debbfaec51a9b12ca529f167d51c473405897d67e16aa76460efe42da64b5
cohort-manager-servicenow-message-handler-vulnerabilities-summary.txt
2.3 KB
sha256:9d0796b59575d1eef2badc09e96c73a61186192621ec0ab452df3a28f0e50e89
cohort-manager-static-validation-vulnerabilities-summary.txt
2.27 KB
sha256:ccc34e8d6ca862a69ecb050b80056db74d2700e271774e659a7af24bb5af9f67
cohort-manager-transform-data-service-vulnerabilities-summary.txt
2.29 KB
sha256:06af2103b5f9cf66e6bd35fb3e359aceca9f7c78b6aade62794d282455d00995
cohort-manager-update-blocked-flag-vulnerabilities-summary.txt
2.28 KB
sha256:3196fc49fc3829df62667a799da0085637eba3c69f83056af810f119bd43a44e
cohort-manager-update-exception-vulnerabilities-summary.txt
2.27 KB
sha256:ad95fbba342d489ddcc3bea5bda63cf6fea56def297f37bf384f797e625300f2
cohort-manager-web-vulnerabilities-summary.txt
511 Bytes
sha256:b416acafae543726c0a54ff6aaed72fd64b1f48994d05eac4308898a9b6adcd5
cohort-manager-wiremock-vulnerabilities-summary.txt
1.59 KB
sha256:c7495c1762ec8873f6e6351711394f667efd28c4ce6bc64b26100774d8251ff4
lines-of-code-report.json.zip
992 Bytes
sha256:85e387f9b9a803a4ab1633656267e9fc49d9f555c59ed7cef187cf0dbca004ca
sbom-audit-writer-repository-report.json.zip
279 KB
sha256:f10fac673bc0eec2b123644a165a2cbb143eff1aad2b6d197ec83da16d7c9fa4
sbom-bs-request-audit-data-service-repository-report.json.zip
279 KB
sha256:16bdfbf9b36abea4b61ce8bec891cc1596c757d9113ef18738ea12dc8ba351db
sbom-cohort-distribution-data-service-repository-report.json.zip
279 KB
sha256:b83f20cc42b3268be09c47b72e914367f7c9292e8b259929a681c6c046fc4838
sbom-create-exception-repository-report.json.zip
279 KB
sha256:214d81fc8998d99fde4aaf22242f4f85ba78063319d373dd3abc9cac835d60b5
sbom-db-migration-repository-report.json.zip
279 KB
sha256:ba4918d1170aaae3b9b3c86943ef3d870ffa7dcd586eeb919f32916931cd17a1
sbom-delete-participant-repository-report.json.zip
279 KB
sha256:1966c008ffcc06f063203964a2a29407a1eb815afc6974b390aaf7a2e4377de6
sbom-distribute-participant-repository-report.json.zip
279 KB
sha256:b31c70fe026ac256f92745453b2c395b88ca5073e423d2513ab7d23f76c6707b
sbom-durable-demographic-function-repository-report.json.zip
279 KB
sha256:c9a0280442d2fc4cde8b40030f429ffd8a799e121f6cd369de8010d8eb6bf238
sbom-exception-management-data-service-repository-report.json.zip
279 KB
sha256:f5263118491e76fb6f615ce2ba93bb445482287e473b2042e401d914b9078e50
sbom-gene-code-lkp-data-service-repository-report.json.zip
279 KB
sha256:beee25257d67bd4dfb649aabc80bb4b6f9082681c98f76bbf86c963fbd418a1a
sbom-get-validation-exceptions-repository-report.json.zip
279 KB
sha256:2ebedb40a76330942643a23edcd6187f0df12727c2830850968d29f1b14b24ee
sbom-higher-risk-referral-reason-lkp-data-service-repository-report.json.zip
279 KB
sha256:41425e46135053351df4196a5bb6baf5d8c5d36eca368f7eb08739759f97b0c8
sbom-lookup-validation-repository-report.json.zip
279 KB
sha256:9bc3882a23ad310189419f5565160f7c61cbfe479e5267d810e8d3afa1af1d86
sbom-manage-caas-subscription-repository-report.json.zip
279 KB
sha256:f8d9de527be2a88fe4a02dcf7d83fc39ba65a20ff03e498ec5054cc78d098e2f
sbom-manage-nems-subscription-repository-report.json.zip
279 KB
sha256:604f493f7d48127ba1d07b9aaf6df77dd61deb7bc40aabab0a7b96ec2ec54a47
sbom-manage-participant-repository-report.json.zip
279 KB
sha256:97b898848de6daf30cc778de06337e95f967a539ddf1e92922d512655ab21948
sbom-manage-servicenow-participant-repository-report.json.zip
279 KB
sha256:c61fe7205eafc9d761bec0cfa074f6214be8b03c0d17ca81fa12e3ac9d467d58
sbom-nems-mesh-retrieval-repository-report.json.zip
279 KB
sha256:1a03381f77a6072baf2ec1c158f6d018ef040c06fe0e05abd898c8416f727d94
sbom-nems-subscription-data-service-repository-report.json.zip
279 KB
sha256:029772df3d0d42ffde033a9a77b0d704695ba4a4d7a1d035149d50171357e43a
sbom-participant-demographic-data-service-repository-report.json.zip
279 KB
sha256:e2ad71c357c2ed7492d28307ee0f31421116aca902a39b9e880347960c2434c3
sbom-participant-management-data-service-repository-report.json.zip
279 KB
sha256:4325709862e441b5cb1d82fcf6034d254f41a64df2e8c0bd38deb1062d799be7
sbom-process-nems-update-repository-report.json.zip
279 KB
sha256:d7cd7c4eedbf08ad8dcccf54bb7147b065cf6f87ce787d8115000e5f652d12c8
sbom-receive-caas-file-repository-report.json.zip
279 KB
sha256:466268448fb99d68fcb4d89dbec726bbfc2280b67ea5f619fef31c2f2c982a0e
sbom-reference-data-service-repository-report.json.zip
279 KB
sha256:f508e2f2893a110b7b7993b519ffff4e4f0f450af7f6c47db826701ca5bae241
sbom-remove-dummy-gp-code-repository-report.json.zip
279 KB
sha256:391fd7a157ffb308be7d402be0016cdf0589c8dc0360ddedd8b6a338b99a1cf2
sbom-remove-validation-exception-data-repository-report.json.zip
279 KB
sha256:0482899815371e19b0981104505b1673ed78f7a96b2ad89d6e8aa29126eb7185
sbom-retrieve-cohort-distribution-data-repository-report.json.zip
279 KB
sha256:3172f795c7ee380fad69c11e6bbc74a90f4dfa57be3c4c9cbb3991b08c5abf1f
sbom-retrieve-cohort-request-audit-repository-report.json.zip
279 KB
sha256:a5ab7f8566765d8307d8d483cf9e80ca7618c6f82bf0956048c0513d444cf2d7
sbom-retrieve-mesh-file-repository-report.json.zip
279 KB
sha256:fd7e13a9cb83799b2630e9a1f2207220fac40c96f1691a51eea5cedc94a4b5bc
sbom-retrieve-pds-demographic-repository-report.json.zip
279 KB
sha256:d1679bf01f13332471f890c875d7e97dfb7fa9d58131a4c9a3e768afc8994c6d
sbom-screening-lkp-data-service-repository-report.json.zip
279 KB
sha256:d6deb7eb3b0b3f409e6a4db88f7aed1b41cc432301dbee4f91f98d0882460761
sbom-servicenow-cases-data-service-repository-report.json.zip
279 KB
sha256:02719dc74d1ed0b941f4fae42237e9fac39aeff4b4a4c0dd77c421a5920aa739
sbom-servicenow-cohort-lookup-repository-report.json.zip
279 KB
sha256:78662fcfb7a8f59f375044b9ed8cfee0d407491531a7d73dc67aa1cb790dee2f
sbom-servicenow-message-handler-repository-report.json.zip
279 KB
sha256:a84dce1e139718e98a26c158f9b8acb10ad70f50ed13bec81b693c5d608b9693
sbom-static-validation-repository-report.json.zip
279 KB
sha256:5391e4eb78f4820af32c0ed54e9140af201aacffeeaa7fd54bc62ac139cc3f19
sbom-transform-data-service-repository-report.json.zip
279 KB
sha256:fbfa45abf1ee5cc4b3e54927c7add4af136b94ada0c17405b696d194f7638c09
sbom-update-blocked-flag-repository-report.json.zip
279 KB
sha256:8d874b5b0d96dcf501bca1f1d4053c37fd59fac6361897ad7fbfcf13c1fbf2fa
sbom-update-exception-repository-report.json.zip
279 KB
sha256:6153da6c2a445eb7e2e30ba74d8e9e37b775e566ba0b0677d50a5bcbb6be346c
sbom-web-repository-report.json.zip
279 KB
sha256:f2f06d2634faa07fd43ecf759527a3978ab953b3421e90639c36e388b5455a79
sbom-wiremock-repository-report.json.zip
279 KB
sha256:cb09953cc0aa72d77e84d4abaa932c1a5e8ab432449d60813f27d3d2346c2570
test-coverage-report
318 KB
sha256:0e146d81f37dad212dbfefca75a3e12862ae0dc05bda5b096b6ecab5d660903d
test-results-consolidated
684 KB
sha256:2ec09e84b3f0eabc3a2adf49b59795de79e3c4b9192cca0fe3bdce4616df8eff
vulnerabilities-audit-writer-repository-report.json.zip
27.3 KB
sha256:57179ba865ed19a83b8a60b3d4cea90afaa44072b99a7a35379202175d5d1dca
vulnerabilities-bs-request-audit-data-service-repository-report.json.zip
27.4 KB
sha256:b707daa7eaf8c583ec27035acb1f6b719c50963f1fc6df5149b4db528bd9a967
vulnerabilities-cohort-distribution-data-service-repository-report.json.zip
27.4 KB
sha256:a37307ee3c48f0098f9bd0dac9989b4e97e27a3c84a60865ced3b98e20415549
vulnerabilities-create-exception-repository-report.json.zip
27.3 KB
sha256:a776e49c98f8ab106e1bf9d9e6f6610131d7e226df777181b6ae701899c33677
vulnerabilities-db-migration-repository-report.json.zip
27.3 KB
sha256:1d786dcd73bd2fad0c45bf8f9ea4b7d6c7bdb778a62ebbd20d67d9e41ea57dc8
vulnerabilities-delete-participant-repository-report.json.zip
27.3 KB
sha256:108a28d06232030a9f3253946909991362b424965f634de3dc94c913cb83139e
vulnerabilities-distribute-participant-repository-report.json.zip
27.3 KB
sha256:ce709bf6a1e9b95f9b5ba41ddd7b143a9195af85a2e302f9e1f501dd529bdb60
vulnerabilities-durable-demographic-function-repository-report.json.zip
27.4 KB
sha256:6fc173d3cb094ae6608783d0aa092d7c302184739d5b0ea30916dcf0c9b40a0d
vulnerabilities-exception-management-data-service-repository-report.json.zip
27.4 KB
sha256:e360f1e9a2fdc0faa8b388b5af1087a0fb1a5560b9840acf79520828d560ee8e
vulnerabilities-gene-code-lkp-data-service-repository-report.json.zip
27.3 KB
sha256:7dc6d699945d2367739deb475217c4f904619e70310b76b788b0d7d9620877a1
vulnerabilities-get-validation-exceptions-repository-report.json.zip
27.3 KB
sha256:34a4bbdc3bcbec26ca89feab5e4154741718629c2789629647d6bee9bd7f28c2
vulnerabilities-higher-risk-referral-reason-lkp-data-service-repository-report.json.zip
27.4 KB
sha256:5ee60495af3bf2540526e4bed22eb78669da5e6f0f870ab9cd193cc049e4bd24
vulnerabilities-lookup-validation-repository-report.json.zip
27.3 KB
sha256:5340d9fbfdaa1ece6fd6964f09005e58ff7fe111ffbfd28c7bb59cbb7442d5a7
vulnerabilities-manage-caas-subscription-repository-report.json.zip
27.4 KB
sha256:46a3f150333ce3e54fed916bc2dfec2d591dfe4893f87ed552c04b5960e756dc
vulnerabilities-manage-nems-subscription-repository-report.json.zip
27.3 KB
sha256:dbf49f0044455e4da3e4ca58a8aa23da53e7642fcd1765e2178c2075c65c9c50
vulnerabilities-manage-participant-repository-report.json.zip
27.3 KB
sha256:410485fdafd465680b7b3db0b025b17ebff3b2965fdc61bafda05d81d0e11501
vulnerabilities-manage-servicenow-participant-repository-report.json.zip
27.3 KB
sha256:b943c6a46d35da34cb1b2aa6bf65a3c39dc8e6115392c012b46fb1d5af0e105f
vulnerabilities-nems-mesh-retrieval-repository-report.json.zip
27.3 KB
sha256:043a446655317c5afc66acd4e3bdb0a9a264ccae1016b3dbd29ed2b1a04e4fea
vulnerabilities-nems-subscription-data-service-repository-report.json.zip
27.4 KB
sha256:dd20c117445716c28afe835697c53234bff8e7f7486a2da1f8a5f1e76745f745
vulnerabilities-participant-demographic-data-service-repository-report.json.zip
27.4 KB
sha256:66cdb57a0e2fe27e96260f8075e321c57d278f5071a70e41691344ac20f40f3e
vulnerabilities-participant-management-data-service-repository-report.json.zip
27.4 KB
sha256:65e7082eec847e1e4da5bf1f0be679fc11785ebef6ad72de078fdbc4bb9c2b18
vulnerabilities-process-nems-update-repository-report.json.zip
27.3 KB
sha256:e95ea27e1638876528be19cb0e2f84a57e204c13efa493054582b2e2fb6edb45
vulnerabilities-receive-caas-file-repository-report.json.zip
27.3 KB
sha256:344516f48915ef6b0439891576c9a124efc611e238ca2236eeaff3b3520e0af3
vulnerabilities-reference-data-service-repository-report.json.zip
27.3 KB
sha256:6a57419bb632ba427673ef360cff2a549cb074604f5342cb49ceeba836c9c667
vulnerabilities-remove-dummy-gp-code-repository-report.json.zip
27.3 KB
sha256:143d2ad3ca37d526313e8d61e2fb4413920e62aed422a2aa18d9267d600865f8
vulnerabilities-remove-validation-exception-data-repository-report.json.zip
27.4 KB
sha256:c2bc1e4c17dc44e6db8234bfbe66e74b12cdddc88acae8308b74095ebe95da56
vulnerabilities-retrieve-cohort-distribution-data-repository-report.json.zip
27.4 KB
sha256:455e03152a0240307e4e20d058d2f350465d6a6c6320a671d1ba52180c3abbb9
vulnerabilities-retrieve-cohort-request-audit-repository-report.json.zip
27.4 KB
sha256:52c4d7914c42499d25b9c3a891c039c6a51ec6be6ee29d79dab243c850aff327
vulnerabilities-retrieve-mesh-file-repository-report.json.zip
27.3 KB
sha256:6911efcc339b8ebe2de2a90913da7ada727799c2587d6ff06b9344e16d530fe1
vulnerabilities-retrieve-pds-demographic-repository-report.json.zip
27.3 KB
sha256:8df637e843c17dc66a411d1c3ddba7d0c83a17c68ca4d3b98a551bdb24b7c482
vulnerabilities-screening-lkp-data-service-repository-report.json.zip
27.4 KB
sha256:b5eaf435736fe61a091b27d62d200ccfc3e5fbe6fb8db3667bc6d3cd7935ab90
vulnerabilities-servicenow-cases-data-service-repository-report.json.zip
27.4 KB
sha256:35f45119f4b05fcbeba2e8f5bc7247206777ec38d649d7afe6b109cd4003669c
vulnerabilities-servicenow-cohort-lookup-repository-report.json.zip
27.3 KB
sha256:1f2909b847a3600ddcf0490cedf72e0e3fd2a45689fd06ea1f3143234a672d5c
vulnerabilities-servicenow-message-handler-repository-report.json.zip
27.4 KB
sha256:3cf3134b97e5c24116c188e63a36e05b3ee4ece1bc72ce4df732dc3e953568d4
vulnerabilities-static-validation-repository-report.json.zip
27.3 KB
sha256:3c54fdfac216192cd9a9aca7bece20a3155f43997a09a8eb10a851b3d19322a6
vulnerabilities-transform-data-service-repository-report.json.zip
27.3 KB
sha256:98db82f05703b062be0662286c39ea85b44cba3f728be5a9b59fbe586dea4c17
vulnerabilities-update-blocked-flag-repository-report.json.zip
27.3 KB
sha256:78bda57c4b48e8800e546adfd0bded1b356aec9b6ff02be0a83b4e18840fab73
vulnerabilities-update-exception-repository-report.json.zip
27.3 KB
sha256:2485b5cfdd7b6adbe44cbb044beb7e55e13b64bd401bcdaf4235b5117f2f2903
vulnerabilities-web-repository-report.json.zip
27.3 KB
sha256:1cb915e78c102019ad4502158ce308fc0f5f524292d4e9811f39e6f835f8f449
vulnerabilities-wiremock-repository-report.json.zip
27.3 KB
sha256:8c5b315effbad80be9129680f0bfd3d769600eccd2d6efc86d2cd85ece789798