feat: [DTOSS-12403] merge audit and core pipelines #15160
MacMur85cicd-1-pull-request.yaml
on: pull_request
Set CI/CD metadata
8s
Validate PR title
5s
Commit stage
/
Scan secrets
15s
Commit stage
/
Check file format
33s
Commit stage
/
Check Markdown format
6s
Commit stage
/
Check English usage
29s
Commit stage
/
Lint Terraform
8s
Commit stage
/
Count lines of code
25s
Commit stage
/
Scan dependencies
5s
Test stage
/
Check for consolidated test project
5s
Matrix: Test stage / Unit tests
Image build stage
/
get-functions
7s
Image build stage
/
build-base-images
16s
Matrix: Image build stage / build-and-push
Matrix: deploy-stage / Deploy
Waiting for pending jobs
Acceptance stage
/
Contract test
4s
Acceptance stage
/
Security test
7s
Acceptance stage
/
UI test
5s
Acceptance stage
/
UI performance test
4s
Acceptance stage
/
Integration test
6s
Acceptance stage
/
Accessibility test
3s
Acceptance stage
/
Load test
4s
Acceptance stage
/
Environment tear down
4s
Annotations
122 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. 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/
|
|
Set CI/CD metadata
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Commit stage / Check Markdown format
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Commit stage / Scan dependencies
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Commit stage / Lint Terraform
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Commit stage / Scan secrets
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Commit stage / Check English usage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Commit stage / Check file format
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test stage / Check for consolidated test project
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test stage / Linting
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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/checkout@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. 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/Configuration/MailboxConfigurationResolver.cs#L14
Converting null literal or possible null value to non-nullable type.
|
|
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/checkout@v4, 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. 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/checkout@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. 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#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/Models/MessageMetaData.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/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/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/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/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 / get-functions
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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: actions/checkout@v4, docker/login-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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/checkout@v4, actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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/checkout@v4, actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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 (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/checkout@v4, actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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 (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/checkout@v4, actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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 (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/checkout@v4, actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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 (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/checkout@v4, actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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 (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/checkout@v4, actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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 (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/checkout@v4, actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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 (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/checkout@v4, actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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 (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/checkout@v4, actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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-servicenow-participant)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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 (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/checkout@v4, actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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 (lookup-validation)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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 (update-exception)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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 (static-validation)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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 (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/checkout@v4, actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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 (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/checkout@v4, actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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 (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/checkout@v4, actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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 (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/checkout@v4, actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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 (create-exception)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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 (distribute-participant)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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/checkout@v4, actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Image build stage / build-and-push (web)
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/checkout@v4, actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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 (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/checkout@v4, actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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 (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/checkout@v4, actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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 (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/checkout@v4, actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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 (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/checkout@v4, actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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 (manage-participant)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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 (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/checkout@v4, actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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 (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/checkout@v4, actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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/checkout@v4, actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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 (retrieve-pds-demographic)
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/checkout@v4, actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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 (delete-participant)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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 (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/checkout@v4, actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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 (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/checkout@v4, actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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 (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/checkout@v4, actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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 (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/checkout@v4, actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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 (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/checkout@v4, actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Image build stage / build-and-push (manage-nems-subscription)
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. 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/
|
|
Acceptance stage / Environment set up
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Acceptance stage / Contract test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Acceptance stage / Accessibility test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Acceptance stage / Load test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Acceptance stage / UI performance test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Acceptance stage / UI test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Acceptance stage / Integration test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Acceptance stage / Security test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Acceptance stage / Environment tear down
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
aggregated-sbom-repository-report-pr1865.zip
|
10.2 MB |
sha256:5502c083eb3499a0a377d8f10d2ee97458f86c042fdedb204e71bf8b32dc3c3e
|
|
|
aggregated-vulnerabilities-repository-report-pr1865.zip
|
382 KB |
sha256:c5786d4a4497a3b13de1ace77997fface65dea4dff2bc15f257d093b31a8ccab
|
|
|
cohort-manager-bs-request-audit-data-service-vulnerabilities-summary.txt
Expired
|
1.55 KB |
sha256:469b5eaf93090c5b87f061384294b37f1a7c4f7a00a4225a480292437970f5a0
|
|
|
cohort-manager-cohort-distribution-data-service-vulnerabilities-summary.txt
Expired
|
1.55 KB |
sha256:964b3096b7f756fc162e65587fce345e5b42b9179e50be96a1e3fa56ad610015
|
|
|
cohort-manager-create-exception-vulnerabilities-summary.txt
Expired
|
1.51 KB |
sha256:d7a33bf761d859d68f4f06aca1da9be36c1326b7253b635f4cae9219ae1d94d6
|
|
|
cohort-manager-db-migration-vulnerabilities-summary.txt
Expired
|
1.3 KB |
sha256:8a610130b626217a9011ab2ddada5d03613f422c87dffb6b1798991f3ff703a5
|
|
|
cohort-manager-delete-participant-vulnerabilities-summary.txt
Expired
|
1.52 KB |
sha256:fc1247583d47b1add6876b5689b186c1afd1a1b1d294bdc99a7aec5e097ddff8
|
|
|
cohort-manager-distribute-participant-vulnerabilities-summary.txt
Expired
|
1.53 KB |
sha256:2ea44f63aeb730a7dc52c012fa2618c37b8077fce6679e396bd2a07323ac3813
|
|
|
cohort-manager-durable-demographic-function-vulnerabilities-summary.txt
Expired
|
1.55 KB |
sha256:bce1e5aa200292c149426743106d585d8e98c68d16ca71b37ed17150dafb5d95
|
|
|
cohort-manager-exception-management-data-service-vulnerabilities-summary.txt
Expired
|
1.55 KB |
sha256:5edea4b8417ddf8cbe8845c0a216db28e8caa153b85c94dad4f5770b3d1f1062
|
|
|
cohort-manager-gene-code-lkp-data-service-vulnerabilities-summary.txt
Expired
|
1.54 KB |
sha256:0f29b3143e1cc1dbb4b2ebd895910f5061606df94fb9b61f65a27753b49af8b3
|
|
|
cohort-manager-get-validation-exceptions-vulnerabilities-summary.txt
Expired
|
1.54 KB |
sha256:d3687dccb441ac6c4b2f14cdddb0451d2e24e7fb314adc96fdfbb22ec67a5eeb
|
|
|
cohort-manager-higher-risk-referral-reason-lkp-data-service-vulnerabilities-summary.txt
Expired
|
1.59 KB |
sha256:06643cf1cdad7fca5414a12582747a968e048a8a6bd9b5fae95c8b73d1c6f853
|
|
|
cohort-manager-lookup-validation-vulnerabilities-summary.txt
Expired
|
1.52 KB |
sha256:47a49fa8f39258bfeb3974259e365bcbcc3db20d6c16b052f15f47016981da26
|
|
|
cohort-manager-manage-caas-subscription-vulnerabilities-summary.txt
Expired
|
1.53 KB |
sha256:dd930e328c9776fd0e1d2c83c96f2c18bf826e5aaa6a60d93bd6a271064543e3
|
|
|
cohort-manager-manage-nems-subscription-vulnerabilities-summary.txt
Expired
|
1.53 KB |
sha256:882227cf1faaf1527b39145a4077fa3ff32ef3eaadf941db060996b25f80c313
|
|
|
cohort-manager-manage-participant-vulnerabilities-summary.txt
Expired
|
1.52 KB |
sha256:53d7da066f6a852eda9afbb1ecd9e039ec43ede279e0ad7c3cb54c6c8b129f9d
|
|
|
cohort-manager-manage-servicenow-participant-vulnerabilities-summary.txt
Expired
|
1.54 KB |
sha256:f00a83ce76ca30453d0bb320f52d9a966d1988c45c3f6a61602dccc82eb86a43
|
|
|
cohort-manager-nems-mesh-retrieval-vulnerabilities-summary.txt
Expired
|
1.52 KB |
sha256:ce80806b234343d7037a864f0e66613b802aa4416abba1e88a3704a0dcae33f2
|
|
|
cohort-manager-nems-subscription-data-service-vulnerabilities-summary.txt
Expired
|
1.55 KB |
sha256:c5199300eab48b87c91405fa4091c30a3c1b5f549b840ecc8ed73ef65267cb68
|
|
|
cohort-manager-participant-demographic-data-service-vulnerabilities-summary.txt
Expired
|
1.57 KB |
sha256:ed2de7f704c7162a71f75a55cd0db6ddb8ecd8972f42046fa393998e355900bc
|
|
|
cohort-manager-participant-management-data-service-vulnerabilities-summary.txt
Expired
|
1.56 KB |
sha256:e371c9bdc34ecbbaf629c8718faf7458c17bbce6ea7d66fe62f4957c8c4f8bf8
|
|
|
cohort-manager-process-nems-update-vulnerabilities-summary.txt
Expired
|
1.52 KB |
sha256:c9e3c685d49ffa54dd4aedccab659964f64a256679bf0219d10a6f771c1a6a16
|
|
|
cohort-manager-receive-caas-file-vulnerabilities-summary.txt
Expired
|
1.52 KB |
sha256:c7b30b5796ed2093d4c73231a20ca5b9a67a95775fa7f4c638d85cf1dddc87e1
|
|
|
cohort-manager-reference-data-service-vulnerabilities-summary.txt
Expired
|
1.53 KB |
sha256:24e0d21050c7a4d47e368012a9d02c81a765287cccf1d223dd4db60e2eeb3b4e
|
|
|
cohort-manager-remove-validation-exception-data-vulnerabilities-summary.txt
Expired
|
1.55 KB |
sha256:bdae4945f5b0885e0d9e3f2b5449e34cc985a614ed8dae7f770a5c7b099120b7
|
|
|
cohort-manager-retrieve-cohort-distribution-data-vulnerabilities-summary.txt
Expired
|
1.55 KB |
sha256:ed57434e9f3cb3a582ed5f42c3f053a72024d01ca179c5e32148dc917d6ee6eb
|
|
|
cohort-manager-retrieve-cohort-request-audit-vulnerabilities-summary.txt
Expired
|
1.54 KB |
sha256:9daea74a3f70dc9a70bde96f20d9f59ba2bb3a480baa8e00183ef1a3377bd83f
|
|
|
cohort-manager-retrieve-mesh-file-vulnerabilities-summary.txt
Expired
|
1.52 KB |
sha256:bdc9ce98c1f27b77439fb87341535d0401d990e6ed70986cf2829e76209c5ed8
|
|
|
cohort-manager-retrieve-pds-demographic-vulnerabilities-summary.txt
Expired
|
1.53 KB |
sha256:fdbc1363a8e7e93524ec74e55269856a24c9447becc573372ba7fe8266f91005
|
|
|
cohort-manager-screening-lkp-data-service-vulnerabilities-summary.txt
Expired
|
1.54 KB |
sha256:5b1607446b838d2eb0b26e956159a64e7080d19ccb10ce39e6e8a68e52318fda
|
|
|
cohort-manager-servicenow-cases-data-service-vulnerabilities-summary.txt
Expired
|
1.54 KB |
sha256:489136690eda2fc7c9dceee0b31945cb657deafb9ec8c53cc4cc9e5fe8e569c8
|
|
|
cohort-manager-servicenow-cohort-lookup-vulnerabilities-summary.txt
Expired
|
1.53 KB |
sha256:42c7ec6cee01cde8b7573e79c44283d5c817e97d3b2ddcb50d3f0d218901f8f3
|
|
|
cohort-manager-servicenow-message-handler-vulnerabilities-summary.txt
Expired
|
1.54 KB |
sha256:da16ae0d18e2abeb7cbdfbea3989287e6cea2cfce0ed75e1b17a86d9b764a412
|
|
|
cohort-manager-static-validation-vulnerabilities-summary.txt
Expired
|
1.52 KB |
sha256:04712e68f6041811273189659ef5be1a3d9a7b2886bb261c97b9d227f8dc5662
|
|
|
cohort-manager-transform-data-service-vulnerabilities-summary.txt
Expired
|
1.53 KB |
sha256:e144804ff471b99fc9228833586eb99a6aa76fb0e588c515a29d1d3ef062dc4a
|
|
|
cohort-manager-update-blocked-flag-vulnerabilities-summary.txt
Expired
|
1.52 KB |
sha256:8b4c4fb442bdd92378245bcf863f30adcbdeed68d9145add139ee9fff2ce5933
|
|
|
cohort-manager-update-exception-vulnerabilities-summary.txt
Expired
|
1.51 KB |
sha256:fe4d8cb1aa33f3398c431cba00c0ef0054f3e8a8f9bfe5d397498107acc7c58a
|
|
|
cohort-manager-web-vulnerabilities-summary.txt
Expired
|
816 Bytes |
sha256:6a769b3af4c513e86c0dbd7134995600350c5450596f1776e04eb81b4ef3f77b
|
|
|
cohort-manager-wiremock-vulnerabilities-summary.txt
Expired
|
841 Bytes |
sha256:06ad6d1105dea283967ef00c5a2aa1b437732a8da5950a3165147857c23ed851
|
|
|
lines-of-code-report.json.zip
Expired
|
975 Bytes |
sha256:76fb934d8590f9f3e0df4310852513da46a175072617b4be44077f5f24b5e7ec
|
|
|
sbom-bs-request-audit-data-service-repository-report.json.zip
Expired
|
274 KB |
sha256:6d12b73f4abac720fb33581d1fc8e6180a980713e1f5b713fa3f439e0d2cd753
|
|
|
sbom-cohort-distribution-data-service-repository-report.json.zip
Expired
|
274 KB |
sha256:109faff336ccf3e45181ed71d2ddee5049851deee7ed937374ffdb4f55aaae51
|
|
|
sbom-create-exception-repository-report.json.zip
Expired
|
274 KB |
sha256:46b6e6e6c1c38c6ea92538cf47e34ba0efd21a2f7052e780aae2fd3fb59d7344
|
|
|
sbom-db-migration-repository-report.json.zip
Expired
|
274 KB |
sha256:cfbebd98b77888eb83e2682a3811c2984e9f7233c01804df62c9914770a529a2
|
|
|
sbom-delete-participant-repository-report.json.zip
Expired
|
274 KB |
sha256:4bde275704c9d4f20eee851ae19b63c61eb02e380332df49404e56b5abb47771
|
|
|
sbom-distribute-participant-repository-report.json.zip
Expired
|
274 KB |
sha256:24a1af6248697df4d56665a90dc2263e20d59c8f94ec4f5aa3d0a1410dd31c38
|
|
|
sbom-durable-demographic-function-repository-report.json.zip
Expired
|
274 KB |
sha256:6fe7e3aca488b3e87655e06c800c56153dc8f7f32bcc1370e2517386d1451f21
|
|
|
sbom-exception-management-data-service-repository-report.json.zip
Expired
|
274 KB |
sha256:5842bdbe8388191366b9c407d5c9b32905bd1092a01edd9825fd18921fb5b26c
|
|
|
sbom-gene-code-lkp-data-service-repository-report.json.zip
Expired
|
274 KB |
sha256:c382b761d9c9ea1d4249f8df7a1d380f952ae077dfbbe35355a54463a098027a
|
|
|
sbom-get-validation-exceptions-repository-report.json.zip
Expired
|
274 KB |
sha256:d854429300cfdfc7dba15045504c45f621061aa7a97e9d48a47430a8cc8bf5e1
|
|
|
sbom-higher-risk-referral-reason-lkp-data-service-repository-report.json.zip
Expired
|
274 KB |
sha256:e017df86f2bb3df8d945b8b10f7a491f4de65329c8150151a20649dd0b64a725
|
|
|
sbom-lookup-validation-repository-report.json.zip
Expired
|
274 KB |
sha256:bebd171cbce6a8a76a1fea2ea8782d8c8db186ef8d549d2ee873d2509521c732
|
|
|
sbom-manage-caas-subscription-repository-report.json.zip
Expired
|
274 KB |
sha256:719ff0721cae2c3b723328cb8c4f4f22d948d0219fdebce036343239ba044054
|
|
|
sbom-manage-nems-subscription-repository-report.json.zip
Expired
|
274 KB |
sha256:a83d1765048619a381a8e4da8face316a0db1dd94d97dfdfc1084f13a4c99d87
|
|
|
sbom-manage-participant-repository-report.json.zip
Expired
|
274 KB |
sha256:ae7c0595613d8424f9080caa6ef95effc837f7037bd4d27dc13d87f78d391031
|
|
|
sbom-manage-servicenow-participant-repository-report.json.zip
Expired
|
274 KB |
sha256:74ac86c837563c4e22bc478c9e9481f8c16270f127a2aa2ccacb347186948216
|
|
|
sbom-nems-mesh-retrieval-repository-report.json.zip
Expired
|
274 KB |
sha256:0c4bc74ab732e34917739c8b4c65a86f53ece2e7aa506f83e1a2b8771fe68e7e
|
|
|
sbom-nems-subscription-data-service-repository-report.json.zip
Expired
|
274 KB |
sha256:d243c1119831709857a81317d778e2a2a5ae5c7f4f31ddaa5d45df3b955677b3
|
|
|
sbom-participant-demographic-data-service-repository-report.json.zip
Expired
|
274 KB |
sha256:f05ca633a53dd5c89b4dfd10b8e84c1d3f356a2a116dec01036a19b29b9701a7
|
|
|
sbom-participant-management-data-service-repository-report.json.zip
Expired
|
274 KB |
sha256:bf294be7fb3e2d31961604780ec3199d2a0dfd06ecf35368dba8bbf657430a3f
|
|
|
sbom-process-nems-update-repository-report.json.zip
Expired
|
274 KB |
sha256:2f7c20f9d2bc2c9efadd77d1f1c937053a8260736ddfaca777ad9c4a331d3c46
|
|
|
sbom-receive-caas-file-repository-report.json.zip
Expired
|
274 KB |
sha256:2dbd77e10e509099f3489ae78c7d07af0fa44467a54fdb3d272bed057b8c3e3e
|
|
|
sbom-reference-data-service-repository-report.json.zip
Expired
|
274 KB |
sha256:dbc08a874743b42d1de329b109e23ea6c67e20790e44652d6e371913dd1c46d3
|
|
|
sbom-remove-validation-exception-data-repository-report.json.zip
Expired
|
274 KB |
sha256:a961b1ecb0228b9dff76e9648e7b9e29f784d161d57ca71f7926f9e891920f29
|
|
|
sbom-retrieve-cohort-distribution-data-repository-report.json.zip
Expired
|
274 KB |
sha256:7b511f89d0271cdcae89bf5acae8ca2dfd4689627db14ab6b5f10d6b17124707
|
|
|
sbom-retrieve-cohort-request-audit-repository-report.json.zip
Expired
|
274 KB |
sha256:d51e1ea14e627449479fa4c219e5c049455375c4543867d6fb3a130245cb100d
|
|
|
sbom-retrieve-mesh-file-repository-report.json.zip
Expired
|
274 KB |
sha256:74e1a21e58cc5c898d1c1499c03f7477af4df71c5aa9057d7b90d860059f8203
|
|
|
sbom-retrieve-pds-demographic-repository-report.json.zip
Expired
|
274 KB |
sha256:44941730d471003ae4909d325d41c8cb9e115c03f903b8287ed63363d06a163e
|
|
|
sbom-screening-lkp-data-service-repository-report.json.zip
Expired
|
274 KB |
sha256:a8f6540fd598e714e224b6287ecefadbafe5e7b21a02e6f1b7e4727465cf1e41
|
|
|
sbom-servicenow-cases-data-service-repository-report.json.zip
Expired
|
274 KB |
sha256:cedad6397270885d1698214f8ad02c5c152481f441eef065758039b8a5af4e72
|
|
|
sbom-servicenow-cohort-lookup-repository-report.json.zip
Expired
|
274 KB |
sha256:699e692fc14db1d40d74568df4218255cf310099d94824b8450f7e9d4f042bad
|
|
|
sbom-servicenow-message-handler-repository-report.json.zip
Expired
|
274 KB |
sha256:e884b5528a4b4e480351da9f4f97d1508b36e1728414a72194292d9a9054f3ed
|
|
|
sbom-static-validation-repository-report.json.zip
Expired
|
274 KB |
sha256:74a112db4fb1da015e600efd26a986a952d1e8ab43aa9866c3f26eefe6fcc3d8
|
|
|
sbom-transform-data-service-repository-report.json.zip
Expired
|
274 KB |
sha256:e43401e585985d55258a6b50ed0a74f961d1c904829b42003c6c5793bc203228
|
|
|
sbom-update-blocked-flag-repository-report.json.zip
Expired
|
274 KB |
sha256:f7e011a6992870212c10b4126d6d9bab2ba5f92939c2e495a9e8c7da364afc1a
|
|
|
sbom-update-exception-repository-report.json.zip
Expired
|
274 KB |
sha256:f6247abcd853c1525a54dc9326e2c49a203f540f931e0484760817a501102c68
|
|
|
sbom-web-repository-report.json.zip
Expired
|
274 KB |
sha256:052075da119af4fd7c2e4acedce8782cc06071298b35d3fc8bd36fd5be12075c
|
|
|
sbom-wiremock-repository-report.json.zip
Expired
|
274 KB |
sha256:250eb52767c23deb28ebacb4428f464b8f98aaa3334726bac18720c20aed1ce1
|
|
|
test-coverage-report
|
296 KB |
sha256:6f4c0389535d627b45a30394d2c0520793cf69da4151fae2f18aa0429e66db05
|
|
|
test-results-consolidated
|
639 KB |
sha256:ea93b35fd9a642774eaaccaf9edc4111cc020ce245a69934b230ff85b418418a
|
|
|
vulnerabilities-bs-request-audit-data-service-repository-report.json.zip
Expired
|
28.2 KB |
sha256:26445b0784f6c7bd8ec11aab95e8ea16ea23f542e4a7d690cf1615ebda01d5ac
|
|
|
vulnerabilities-cohort-distribution-data-service-repository-report.json.zip
Expired
|
28.2 KB |
sha256:b3439e66b313d33ff2a8ffe15feb948a48d1522fa0c0ba3cdea675c65deb47a6
|
|
|
vulnerabilities-create-exception-repository-report.json.zip
Expired
|
28.2 KB |
sha256:e41d03be61a0b450278e95eaf73e4b2df051ebbc2571bd51720e4111e0d6c614
|
|
|
vulnerabilities-db-migration-repository-report.json.zip
Expired
|
28.2 KB |
sha256:cfdb110517ef8744674de40bdc80c59a157c206fddd313f43fbbff1d504b6df5
|
|
|
vulnerabilities-delete-participant-repository-report.json.zip
Expired
|
28.2 KB |
sha256:42bcc6e1a5290a09f9c7c90af490f21ac5f95485b8193dde6eb77ad2a2f8eec1
|
|
|
vulnerabilities-distribute-participant-repository-report.json.zip
Expired
|
28.2 KB |
sha256:04dd948deb06ad60b970662de73eb698262c1f4299863714fbdd15000a715469
|
|
|
vulnerabilities-durable-demographic-function-repository-report.json.zip
Expired
|
28.2 KB |
sha256:f59ac52ad3052c116bcbe67b872045880a775491bf97adcaac97eedafbebc673
|
|
|
vulnerabilities-exception-management-data-service-repository-report.json.zip
Expired
|
28.2 KB |
sha256:6c54390df5010fbf4c0418febfce7e59f86639289bc86fdd283c325e944b22cd
|
|
|
vulnerabilities-gene-code-lkp-data-service-repository-report.json.zip
Expired
|
28.2 KB |
sha256:8b931c95caae7e0f2ecee6884267a66cbf56bb24952bb795bf3eacbddfa032d8
|
|
|
vulnerabilities-get-validation-exceptions-repository-report.json.zip
Expired
|
28.2 KB |
sha256:6437690f1d71164a64b19fb7c4bb37bd8cec9e721b9b92ee982bdc712e34686e
|
|
|
vulnerabilities-higher-risk-referral-reason-lkp-data-service-repository-report.json.zip
Expired
|
28.3 KB |
sha256:710f4e0953671241259557d054fe29fe20fa41ab4c2872ccac8c7b185031dbd0
|
|
|
vulnerabilities-lookup-validation-repository-report.json.zip
Expired
|
28.2 KB |
sha256:f779cc21b3cece7aa6bcd5b88fcf42d4d6f2a3a5f3347fca0f1fd66b5101b1b1
|
|
|
vulnerabilities-manage-caas-subscription-repository-report.json.zip
Expired
|
28.2 KB |
sha256:530891dd7ede45d78a7c87680a9bcc97ab64ffae32d3dc1c4ccc32ff3be489e9
|
|
|
vulnerabilities-manage-nems-subscription-repository-report.json.zip
Expired
|
28.2 KB |
sha256:6b9eee2b849ab5711595fd51ed8ff66c76c014c1b96628dc14df0e9ac0abbf3e
|
|
|
vulnerabilities-manage-participant-repository-report.json.zip
Expired
|
28.2 KB |
sha256:1dac15fa81199f807ca8885d1ee4a3de026bc21696b7e033c5585827adc13d22
|
|
|
vulnerabilities-manage-servicenow-participant-repository-report.json.zip
Expired
|
28.2 KB |
sha256:6c668e8ee86665e39a7b963532b472f0775feaf61be1af2f649033e505826085
|
|
|
vulnerabilities-nems-mesh-retrieval-repository-report.json.zip
Expired
|
28.2 KB |
sha256:5e36051a1b9bbf612289f5e2b45699f938fe013155f2f279d903dd740a59c1fa
|
|
|
vulnerabilities-nems-subscription-data-service-repository-report.json.zip
Expired
|
28.2 KB |
sha256:f3fd6b110f1a06e58b97f99c667a05ebb768c8ff76d761129af950c6f26d5a04
|
|
|
vulnerabilities-participant-demographic-data-service-repository-report.json.zip
Expired
|
28.3 KB |
sha256:6e066005c1972d3ceb15f8f19b817f9421e827210ab1329078f919acc58d6c3c
|
|
|
vulnerabilities-participant-management-data-service-repository-report.json.zip
Expired
|
28.3 KB |
sha256:3719e5258fc17e05d5ec7cfa92cb83f12d6a460decfd81162f29d79e2dd7c9e2
|
|
|
vulnerabilities-process-nems-update-repository-report.json.zip
Expired
|
28.2 KB |
sha256:8d572bd0ac581432389e7ec6579b7d431124c5403f4b977ae7f26b529be5d894
|
|
|
vulnerabilities-receive-caas-file-repository-report.json.zip
Expired
|
28.2 KB |
sha256:112d7f0ad132343c64476971539562503afe2f5be1742b83260fafff482d3f17
|
|
|
vulnerabilities-reference-data-service-repository-report.json.zip
Expired
|
28.2 KB |
sha256:0398be32d6536df1c0ad87dd3d877a6d27bc4db01a6fc4459dbdff3ca5c2550f
|
|
|
vulnerabilities-remove-validation-exception-data-repository-report.json.zip
Expired
|
28.2 KB |
sha256:a5d15479f7126151a188f1ba542bc8fe1fd8adcee2f4f6909d33f75719be2113
|
|
|
vulnerabilities-retrieve-cohort-distribution-data-repository-report.json.zip
Expired
|
28.3 KB |
sha256:39dc7ada9826b5b69218d868ac4a77ec65e77ad67d0f9e0bf513cdf2510b6c08
|
|
|
vulnerabilities-retrieve-cohort-request-audit-repository-report.json.zip
Expired
|
28.2 KB |
sha256:afd1c69d488abb54b1c8dcde23afe7a71fd6e924c0df910cce72a4cbaa78a9a2
|
|
|
vulnerabilities-retrieve-mesh-file-repository-report.json.zip
Expired
|
28.2 KB |
sha256:08f6e0cf305587f8b11635eebdf934f12915c8dd838c2104f69cc9427c8e57db
|
|
|
vulnerabilities-retrieve-pds-demographic-repository-report.json.zip
Expired
|
28.2 KB |
sha256:cce9233a0af9030b1862c52d607305aba51c0985a5eecb4747f8e188a239c327
|
|
|
vulnerabilities-screening-lkp-data-service-repository-report.json.zip
Expired
|
28.2 KB |
sha256:a8a60befaece0732ede5bec7c2d09664e76416d8e17bfead41de36bf07f79a75
|
|
|
vulnerabilities-servicenow-cases-data-service-repository-report.json.zip
Expired
|
28.2 KB |
sha256:1bc7d58f686afb09c2e3ba56ef2ede96362a67a5b8bbf412b8c460d643d58346
|
|
|
vulnerabilities-servicenow-cohort-lookup-repository-report.json.zip
Expired
|
28.2 KB |
sha256:27f6b59466e5725bb976dc70f4abce384349094194db332370b93b068a9f4ac2
|
|
|
vulnerabilities-servicenow-message-handler-repository-report.json.zip
Expired
|
28.2 KB |
sha256:dea23dce24c2085a2df8862cadae629053345999d2db726a4c2c489a2d35ef7a
|
|
|
vulnerabilities-static-validation-repository-report.json.zip
Expired
|
28.2 KB |
sha256:6d67938263a718095cb866cd6f69dfca39d798142519d2316511ba83505b7448
|
|
|
vulnerabilities-transform-data-service-repository-report.json.zip
Expired
|
28.2 KB |
sha256:465535c498ee1888768676f687d889256f43f0985a88abae3d9c9d2d5b441e67
|
|
|
vulnerabilities-update-blocked-flag-repository-report.json.zip
Expired
|
28.2 KB |
sha256:bf3dcf20303e07aa421be7cb1cabc0b8326b80eeb40c9e80e46c2a8846e22605
|
|
|
vulnerabilities-update-exception-repository-report.json.zip
Expired
|
28.2 KB |
sha256:a23d6ab8e3c7a146c0c70ad5acb387d003c2ab38b3d8f21647243187e63da974
|
|
|
vulnerabilities-web-repository-report.json.zip
Expired
|
28.2 KB |
sha256:e3bca3a7bc90abd58045719393d084cb466cd1cf3ab64105e8a9eacc05a19887
|
|
|
vulnerabilities-wiremock-repository-report.json.zip
Expired
|
28.2 KB |
sha256:2036d8e74e12005b7e88a07d015cfddc22f05ec9183d6597e5c40bf659667c6d
|
|