feat: [DTOSS-12154] disabled shared access key for storage account and enabled use managed identity for storage account #15488
nc-shahidazimcicd-1-pull-request.yaml
on: pull_request
Set CI/CD metadata
6s
Validate PR title
6s
Commit stage
/
Scan secrets
14s
Commit stage
/
Check file format
11s
Commit stage
/
Check Markdown format
6s
Commit stage
/
Check English usage
10s
Commit stage
/
Lint Terraform
7s
Commit stage
/
Count lines of code
6s
Test stage
/
Check for consolidated test project
6s
Matrix: Test stage / Unit tests
Image build stage
/
get-functions
9s
Image build stage
/
build-base-images
2m 9s
Matrix: Image build stage / build-and-push
Matrix: deploy-stage / Deploy
Waiting for pending jobs
Annotations
107 warnings
|
Validate PR title
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: amannn/action-semantic-pull-request@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Commit stage / Count lines of code
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test stage / Run consolidated tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test stage / Run consolidated tests:
application/CohortManager/src/Functions/Shared/dotnet-mesh-client/application/DotNetMeshClient/NHS.Mesh.Client/Models/Response/OutboxService/TrackOutboxResponse.cs#L15
Non-nullable property 'ExpiryTime' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
|
Test stage / Run consolidated tests:
application/CohortManager/src/Functions/Shared/dotnet-mesh-client/application/DotNetMeshClient/NHS.Mesh.Client/Models/Response/OutboxService/TrackOutboxResponse.cs#L13
Non-nullable property 'FileName' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
|
Test stage / Run consolidated tests:
application/CohortManager/src/Functions/Shared/dotnet-mesh-client/application/DotNetMeshClient/NHS.Mesh.Client/Models/Response/OutboxService/TrackOutboxResponse.cs#L7
Non-nullable property 'MessageId' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
|
Test stage / Run consolidated tests:
application/CohortManager/src/Functions/Shared/dotnet-mesh-client/application/DotNetMeshClient/NHS.Mesh.Client/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.
|
|
Test stage / Run consolidated tests:
application/CohortManager/src/Functions/Shared/dotnet-mesh-client/application/DotNetMeshClient/NHS.Mesh.Client/Models/Response/APIErrorResponse.cs#L11
Non-nullable property 'ErrorDescription' 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/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.
|
|
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 / Run consolidated tests:
application/CohortManager/src/Functions/Shared/dotnet-mesh-client/application/DotNetMeshClient/NHS.Mesh.Client/Models/FileAttachment.cs#L7
Non-nullable property 'ContentType' 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/FileAttachment.cs#L6
Non-nullable property 'Content' 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/FileAttachment.cs#L5
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 / 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/Configuration/MailboxConfigurationResolver.cs#L14
Converting null literal or possible null value to non-nullable type.
|
|
Analysis stage / Perform static analysis:
application/CohortManager/src/Functions/Shared/dotnet-mesh-client/application/DotNetMeshClient/NHS.Mesh.Client/Configuration/MeshConnectConfiguration.cs#L51
Non-nullable property 'ProxyAddress' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Image build stage / build-base-images
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Image build stage / build-and-push (wiremock)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Image build stage / build-and-push (wiremock)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
|
|
Image build stage / build-and-push (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (create-exception)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Image build stage / build-and-push (create-exception)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
|
|
Image build stage / build-and-push (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (exception-management-data-service)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Image build stage / build-and-push (exception-management-data-service)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
|
|
Image build stage / build-and-push (manage-participant)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, anchore/scan-action@56e320f818c551f3f035fde89894504f269ad30b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Image build stage / build-and-push (manage-participant)
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
|
|
Image build stage / 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 (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 (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 (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 (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 (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 / aggregate-json
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
aggregated-sbom-repository-report-pr1882.zip
|
10.9 MB |
sha256:71e0e9b15a9e75c9bc2026fa6a98311d76b47eca76a58a5d4eecad6233bdfeaf
|
|
|
aggregated-vulnerabilities-repository-report-pr1882.zip
|
585 KB |
sha256:28dfe863f9333b696aa89e75e34726d54309862194430285a8240a540ff7ba0a
|
|
|
cohort-manager-audit-writer-vulnerabilities-summary.txt
|
2.26 KB |
sha256:b829a0b8871b39f75244726fa02c51e1b018cdc81c2ab4a82ddb2abdaabd0fec
|
|
|
cohort-manager-bs-request-audit-data-service-vulnerabilities-summary.txt
|
2.31 KB |
sha256:e274d8d3e8b77eaa98076c76142edcf32d2c62ead8ff0e1a70873329aa5fece4
|
|
|
cohort-manager-cohort-distribution-data-service-vulnerabilities-summary.txt
|
2.31 KB |
sha256:88e48efb990e40b3f0c77a90437f5a65361154911283c12628420015ed1dceb8
|
|
|
cohort-manager-create-exception-vulnerabilities-summary.txt
|
2.27 KB |
sha256:59097a7be4baff0f8ba8e6ccb2b89c3360678120a2073e5558f7b0963d81124a
|
|
|
cohort-manager-db-migration-vulnerabilities-summary.txt
|
1.73 KB |
sha256:741701793ead204a6fce376e1adcc8540ec0298e1a64df2dada4ace24acdda67
|
|
|
cohort-manager-delete-participant-vulnerabilities-summary.txt
|
2.28 KB |
sha256:ab641f46c021156f58da7eb17709d7c375db39ca8efe196e128b0cd462db9f35
|
|
|
cohort-manager-distribute-participant-vulnerabilities-summary.txt
|
2.29 KB |
sha256:3423c053bc28f3762740f468dd113241760cbbc1fccd168dab94600768063288
|
|
|
cohort-manager-durable-demographic-function-vulnerabilities-summary.txt
|
2.31 KB |
sha256:ca4ec7d52561f050b8e317ccba3b09d2c8e3ec3b39172406b97a71949dc0aee6
|
|
|
cohort-manager-exception-management-data-service-vulnerabilities-summary.txt
|
2.31 KB |
sha256:c819ea0cd122a0e0ca574d413405618b87274a8f27391740d8b95b68a96ee1b6
|
|
|
cohort-manager-gene-code-lkp-data-service-vulnerabilities-summary.txt
|
2.3 KB |
sha256:cb53d519101f7af15604eb810e6c289f72fc5a1c74d3acebd3a152f03c9d1ffd
|
|
|
cohort-manager-get-validation-exceptions-vulnerabilities-summary.txt
|
2.29 KB |
sha256:2b54c13215024c7e0afbb13d5eb3179322bbfc8c21569badd981914a3e230fc7
|
|
|
cohort-manager-higher-risk-referral-reason-lkp-data-service-vulnerabilities-summary.txt
|
2.35 KB |
sha256:de016896a5aa1a143f20032326fc8526e2e6a8e530c205277215f166c2f5ddd9
|
|
|
cohort-manager-lookup-validation-vulnerabilities-summary.txt
|
2.27 KB |
sha256:f52688ad5d3510a6d7f113a84b0345aa3003c93b717248c0fbb85efc0170eaba
|
|
|
cohort-manager-manage-caas-subscription-vulnerabilities-summary.txt
|
2.29 KB |
sha256:a111ce4914f92586a3c012f4146428387d40ae975632a6645031ab7cdcedbcd5
|
|
|
cohort-manager-manage-nems-subscription-vulnerabilities-summary.txt
|
2.29 KB |
sha256:fd6b3072f16a90dc0fe88de5da2efff30cc1fdd1a9265d8e653ee8dd76670052
|
|
|
cohort-manager-manage-participant-vulnerabilities-summary.txt
|
2.27 KB |
sha256:5b5198120c4b62b8a24c1e5099fc69f0fe443b92d77fbf6efef582696dc1cf02
|
|
|
cohort-manager-manage-servicenow-participant-vulnerabilities-summary.txt
|
2.3 KB |
sha256:1ad5ca0e2f2384772989fc8d6a512643c4023c75ff4f0401c53f100475a8dded
|
|
|
cohort-manager-nems-mesh-retrieval-vulnerabilities-summary.txt
|
2.28 KB |
sha256:94e10acfa31ee9c0286ea8c0fb5d960029f34ffd7cd231019ff0968ed54f7f22
|
|
|
cohort-manager-nems-subscription-data-service-vulnerabilities-summary.txt
|
2.31 KB |
sha256:86080d59463f1ec32ce238529bbda38e61c611b5a82860e1491fb97b22e4b51b
|
|
|
cohort-manager-participant-demographic-data-service-vulnerabilities-summary.txt
|
2.32 KB |
sha256:7f2eff5550c402f29cbdcca7785c0c9c6767e9d3def30e501f67848c875cab32
|
|
|
cohort-manager-participant-management-data-service-vulnerabilities-summary.txt
|
2.32 KB |
sha256:8be61eab7f8e764946dda3217cd5bc196a3735acf177a6347b3fe3d9a9ce738f
|
|
|
cohort-manager-process-nems-update-vulnerabilities-summary.txt
|
2.28 KB |
sha256:9407aa165f937e7875318ddcce543722d17c8a92bed0c0918a2d995a7a385fbf
|
|
|
cohort-manager-receive-caas-file-vulnerabilities-summary.txt
|
2.27 KB |
sha256:59a145c9ba3e858cf4545d526f7ab1e70a8b3539e92e07e7aebb8a31a6c55598
|
|
|
cohort-manager-reference-data-service-vulnerabilities-summary.txt
|
2.29 KB |
sha256:d0906650d16593e39e185aa0c2af62079ecbba0c3fcdbd98e39c05989619e1fd
|
|
|
cohort-manager-remove-dummy-gp-code-vulnerabilities-summary.txt
|
2.28 KB |
sha256:fa1c4b3b0f3d3072656cd666edbc72f7754f4f824e5ace6987a1edf541793a49
|
|
|
cohort-manager-remove-validation-exception-data-vulnerabilities-summary.txt
|
2.31 KB |
sha256:87bfca9f4999d74c2abb7c1168c96be9b17784ad05042bd36f709bd3c01b0171
|
|
|
cohort-manager-retrieve-cohort-distribution-data-vulnerabilities-summary.txt
|
2.31 KB |
sha256:94b3fa98e79c6fa1e8bdf3137d0c3b90fc3ff73cbfb05b624bf2e237a67aa29a
|
|
|
cohort-manager-retrieve-cohort-request-audit-vulnerabilities-summary.txt
|
2.3 KB |
sha256:bc6fc716227951cf92fb180112ccf944c43f762de770637bbf177adcb7698413
|
|
|
cohort-manager-retrieve-mesh-file-vulnerabilities-summary.txt
|
2.28 KB |
sha256:ddee043f0fb2641f9310c3cb1e5b22478c1d46f9968c324a2b5931d51ec4c919
|
|
|
cohort-manager-retrieve-pds-demographic-vulnerabilities-summary.txt
|
2.29 KB |
sha256:ff0cca177029f6ddd66667393751860122b59268ecc55ed8942d4d7cf73dae54
|
|
|
cohort-manager-screening-lkp-data-service-vulnerabilities-summary.txt
|
2.3 KB |
sha256:d5814fb5e47ca8b6f4a8d364b8cc493f157775431bb107adff2c3b810fdebb11
|
|
|
cohort-manager-servicenow-cases-data-service-vulnerabilities-summary.txt
|
2.3 KB |
sha256:e6004fa1f135460f2fca1fec0d045bfb5854a828084db555d5b9dab0b48482b2
|
|
|
cohort-manager-servicenow-cohort-lookup-vulnerabilities-summary.txt
|
2.29 KB |
sha256:21fbed7e274a8f4ccf652ed7e7e7222d61bea0906f67d099e5bb99cfb7dab56b
|
|
|
cohort-manager-servicenow-message-handler-vulnerabilities-summary.txt
|
2.3 KB |
sha256:373c899f270aa38ba3e59d19373b6e32d0ecc0705839623c4eec186015f678ac
|
|
|
cohort-manager-static-validation-vulnerabilities-summary.txt
|
2.27 KB |
sha256:ffb6a6798ec6fa7001a9e0ef3204e1cfeea60a2e7a40c2d59cd5e7587172fb5d
|
|
|
cohort-manager-transform-data-service-vulnerabilities-summary.txt
|
2.29 KB |
sha256:fb7bf4777647926b46b05fd133c3047bb68eae7ec826656ec3ea70b34e46ac27
|
|
|
cohort-manager-update-blocked-flag-vulnerabilities-summary.txt
|
2.28 KB |
sha256:afc974660bd15af3ab8f928caf9917bd60a902ab7172c016a7ebfa0b1ade6a92
|
|
|
cohort-manager-update-exception-vulnerabilities-summary.txt
|
2.27 KB |
sha256:0663281b1372341add6b3e58a129a300896dfc960b07341e93527f628cffae49
|
|
|
cohort-manager-web-vulnerabilities-summary.txt
|
511 Bytes |
sha256:7c093f8227f18d516ff40b6346199d1a25254e94188f8fa515c571f27220f47c
|
|
|
cohort-manager-wiremock-vulnerabilities-summary.txt
|
1.59 KB |
sha256:cef9cd33080af284a8b1117d180e327cfae6ff67b0ff4be746fb9342393303ab
|
|
|
lines-of-code-report.json.zip
|
992 Bytes |
sha256:a5df6a39736e5117e14fa9de58f43a34eee9c1b545142b57f820aa48bd3b9a02
|
|
|
sbom-audit-writer-repository-report.json.zip
|
279 KB |
sha256:741d0182ceb51a9eb0eb583a491d0dab87ba30f16eaa12d299b7f2561c715d42
|
|
|
sbom-bs-request-audit-data-service-repository-report.json.zip
|
279 KB |
sha256:6b084cacc2a8358cae5159a5e0b318fe353b7661505b464d6b80052fc66c0490
|
|
|
sbom-cohort-distribution-data-service-repository-report.json.zip
|
279 KB |
sha256:2328ec1ce4437d0e5da982bbbe98400d47a103578d0cc699c6ce6a9f897dbc26
|
|
|
sbom-create-exception-repository-report.json.zip
|
279 KB |
sha256:3d04235a40b015d9ab576bb8880cac2cef6167412bc59bd82e42bdd50d4bbbb8
|
|
|
sbom-db-migration-repository-report.json.zip
|
279 KB |
sha256:3d37b20a79e0ae8d69cd079c02d42facf42b8bf259c66735479d774772761fe6
|
|
|
sbom-delete-participant-repository-report.json.zip
|
279 KB |
sha256:f264579e27f5a43d8ededbe93009a52e3d5a50be8fb06d0344b43e9fc8a66768
|
|
|
sbom-distribute-participant-repository-report.json.zip
|
279 KB |
sha256:1199fcba9d236e9f04ba6be3f9024139fd16cfaa61066eefa6cd8f9d3342416c
|
|
|
sbom-durable-demographic-function-repository-report.json.zip
|
279 KB |
sha256:d405bab89512f305740f9cd374a358bcf5cd7be612683843c0c7a68bd9e607b4
|
|
|
sbom-exception-management-data-service-repository-report.json.zip
|
279 KB |
sha256:83987a33c63135c1897475a13c0ae9fc56311b11e993abbd6db4e433829055fd
|
|
|
sbom-gene-code-lkp-data-service-repository-report.json.zip
|
279 KB |
sha256:ef5c2c4f0c54c2c09070e6c5ac34e569184e198d005733ce2b4d3b88f84b387b
|
|
|
sbom-get-validation-exceptions-repository-report.json.zip
|
279 KB |
sha256:2cde5feade7f0c087ea6aa1cac0ac8d0471c48f402b34418b0e453e3f4a46e6d
|
|
|
sbom-higher-risk-referral-reason-lkp-data-service-repository-report.json.zip
|
279 KB |
sha256:a6ea75266b81708198f5723730409137321b6dd355dbe27edbf2a01209b466f7
|
|
|
sbom-lookup-validation-repository-report.json.zip
|
279 KB |
sha256:18ddaf27a26a457595d55493c8f3a6384accb254257bf57ea4d8b3da249329b3
|
|
|
sbom-manage-caas-subscription-repository-report.json.zip
|
279 KB |
sha256:490fb7fb9bc9543bfd3bda141dd9bf821c89cfbb08022bee6491c6c89a652495
|
|
|
sbom-manage-nems-subscription-repository-report.json.zip
|
279 KB |
sha256:49776fed16fe93cda7d7f00cdc30f108a03f2336fbf5f3dd77c30c84e6d7f20d
|
|
|
sbom-manage-participant-repository-report.json.zip
|
279 KB |
sha256:6841bd7cdbc475f119fa9c2d2294b9e0bae228dcd3f80179b786ad7af73ecfca
|
|
|
sbom-manage-servicenow-participant-repository-report.json.zip
|
279 KB |
sha256:40f62f185d9c4039ae2f95582766bce12bb4a732817236f65b8dedb7d32fce8e
|
|
|
sbom-nems-mesh-retrieval-repository-report.json.zip
|
279 KB |
sha256:d288d84dde796057429ba674a9ff654670cee5d883bb1597a3d93515e8d33756
|
|
|
sbom-nems-subscription-data-service-repository-report.json.zip
|
279 KB |
sha256:fc0a8e6e4b19526667eba7e52f7127106e253c5db210f44bd488c156bbe93921
|
|
|
sbom-participant-demographic-data-service-repository-report.json.zip
|
280 KB |
sha256:c7f6d333eba57f3ee6ef90bf81a929a4b2fade6c6c2308cb3a53983abdb17fef
|
|
|
sbom-participant-management-data-service-repository-report.json.zip
|
279 KB |
sha256:a724c872dcdd42f3dfacf88f4413513acbca036723ff62b82ae5b077563d7815
|
|
|
sbom-process-nems-update-repository-report.json.zip
|
279 KB |
sha256:ae033aaba7e2b35846aa51be6f01830b601de7a54a80aa635f9bd16e5539f59e
|
|
|
sbom-receive-caas-file-repository-report.json.zip
|
279 KB |
sha256:808675f22f0de06a2b7c0b47d6ddf2389f391fbbd564295d21de1dcb5ed02ac0
|
|
|
sbom-reference-data-service-repository-report.json.zip
|
279 KB |
sha256:bc4f07bba372aaebcaae57473d1c6a07e0af05e2bad146d752738fc283ba5218
|
|
|
sbom-remove-dummy-gp-code-repository-report.json.zip
|
279 KB |
sha256:72faad1ce84676c9b90613a6a0941a2a87362f7d7e9ca618408b622ab1625736
|
|
|
sbom-remove-validation-exception-data-repository-report.json.zip
|
279 KB |
sha256:27eb91a5522f89d9d85fde3b72dd6c8ff8987779888b9b316a0d02c542a1eb0c
|
|
|
sbom-retrieve-cohort-distribution-data-repository-report.json.zip
|
279 KB |
sha256:957c60572de65e0663ba9b05f8ae4481bcadde64dde42313cef3f80e9fdc8d08
|
|
|
sbom-retrieve-cohort-request-audit-repository-report.json.zip
|
279 KB |
sha256:6b9692785bf5e8ce004afc7be08f5ee81796ce76e83ea160e7c84d04bb932823
|
|
|
sbom-retrieve-mesh-file-repository-report.json.zip
|
279 KB |
sha256:6189dadfa5a898007582fcf446287b4efb2192cd665d6f675293ed8e1c5c89e8
|
|
|
sbom-retrieve-pds-demographic-repository-report.json.zip
|
279 KB |
sha256:ef56815501b2e1ac80bc1454017ec901e88cf8fb9b68fad8beccf7fbd380ec2e
|
|
|
sbom-screening-lkp-data-service-repository-report.json.zip
|
279 KB |
sha256:1b0d1d4e921605ec94090761910f3113ff790853f9d71047a2e33cef41fda3c1
|
|
|
sbom-servicenow-cases-data-service-repository-report.json.zip
|
279 KB |
sha256:987d0bf1bfbec56dd6a30a1d39b53607010f1849660e5ed40e6bfe82af1f1ea1
|
|
|
sbom-servicenow-cohort-lookup-repository-report.json.zip
|
279 KB |
sha256:073df6198193f59a4ad265a4f9dfc1722b75814b637660f4137fb66ab32d58e9
|
|
|
sbom-servicenow-message-handler-repository-report.json.zip
|
279 KB |
sha256:0c5fe853071448526aaab2ebdac0125dfcbec1c38278819fa07d032e4ffd1944
|
|
|
sbom-static-validation-repository-report.json.zip
|
279 KB |
sha256:7823e8e58968d59059f70ab6b32129c1c7079e0e5c39dbcd9b85974da5eaa9ca
|
|
|
sbom-transform-data-service-repository-report.json.zip
|
279 KB |
sha256:a61b5895df9f1bea8452b0060ffb26c95494cdac69fca73da5a262dc2f661127
|
|
|
sbom-update-blocked-flag-repository-report.json.zip
|
279 KB |
sha256:604d06f050497a8457da24a7b4336bdb3aa4f4b836d9e50d02b263e64614dc7b
|
|
|
sbom-update-exception-repository-report.json.zip
|
279 KB |
sha256:66fd8fbd51fd61e4441f8e9a2038c555001a05574bc54af2e57ba9ce156adfc6
|
|
|
sbom-web-repository-report.json.zip
|
279 KB |
sha256:b5affba4b91098c26efad50f00514bd43c323f1a9d294e5688c68cb5c4b5a5ef
|
|
|
sbom-wiremock-repository-report.json.zip
|
279 KB |
sha256:bd64dfabac3cab311175611c82978862da4e33af80f55c6f891e04429fb82986
|
|
|
test-coverage-report
|
322 KB |
sha256:264aec0ebc2f9b2b4d1eb34d3fab8de56183d4dd1f131915c7c32b7a27b3e467
|
|
|
test-results-consolidated
|
691 KB |
sha256:ac70656021e56478bb2c35bd87ea65d4814a456998d4753181cc29de80dd9944
|
|
|
vulnerabilities-audit-writer-repository-report.json.zip
|
27.3 KB |
sha256:e5b9c75c4ad0bcb84367f62b8633b2eb2391c95ed2940d72ff41103145e946db
|
|
|
vulnerabilities-bs-request-audit-data-service-repository-report.json.zip
|
27.4 KB |
sha256:861b4ab55b63771e256b602660ce0f2d368724ad0f85f24536913ca92b558691
|
|
|
vulnerabilities-cohort-distribution-data-service-repository-report.json.zip
|
27.4 KB |
sha256:d89348b53cc8a6e261edf7d1422442f531979035ea38b6d1cfc8003955a2f525
|
|
|
vulnerabilities-create-exception-repository-report.json.zip
|
27.3 KB |
sha256:ed0a013d40859d49647f2ad11a1e01d7890784743f38810faff1a5c334ec1d20
|
|
|
vulnerabilities-db-migration-repository-report.json.zip
|
27.3 KB |
sha256:6ea6c6e9921a37ff8d39832d4c3c60289e996878deab86260f220932560cb48a
|
|
|
vulnerabilities-delete-participant-repository-report.json.zip
|
27.3 KB |
sha256:4dd3f534ed1114f8cf1bd5907dcdc37e77841eeb18d6ce10cae3de41e44e8d9d
|
|
|
vulnerabilities-distribute-participant-repository-report.json.zip
|
27.3 KB |
sha256:fce3d5fa31de0cb493df342cd306f78dc299b3981960451fc9614c83e94d02af
|
|
|
vulnerabilities-durable-demographic-function-repository-report.json.zip
|
27.3 KB |
sha256:cfcdb2c981e1cd842486c96d0ed0b05bfff5c2a9bb2a9f43f493547e4d799d70
|
|
|
vulnerabilities-exception-management-data-service-repository-report.json.zip
|
27.4 KB |
sha256:f732d4f7cb813280e5fa433e95ca81b737e092e718e65090419ed3ac5529e8de
|
|
|
vulnerabilities-gene-code-lkp-data-service-repository-report.json.zip
|
27.4 KB |
sha256:992e6e61159c08c28e23125387a9d55c60e7937ab6ad027e4e1e011b81108636
|
|
|
vulnerabilities-get-validation-exceptions-repository-report.json.zip
|
27.4 KB |
sha256:99028c1edfc721d842bc50db3b3e483a2f9f9c3fb97d26cfefe2ef541d412051
|
|
|
vulnerabilities-higher-risk-referral-reason-lkp-data-service-repository-report.json.zip
|
27.4 KB |
sha256:9a5c2c83fbd46a042c6069ca8aac4c872c901f5bb273bc00cc7f44e0723cc62d
|
|
|
vulnerabilities-lookup-validation-repository-report.json.zip
|
27.3 KB |
sha256:8f63d4564d409307da844fb3c1a0abbfc8bd6da9644ab370d6166678a73203d5
|
|
|
vulnerabilities-manage-caas-subscription-repository-report.json.zip
|
27.3 KB |
sha256:54294797bf7fe5e825f12e822428afc456e8a693581f29c1a94adf2efcbcec1f
|
|
|
vulnerabilities-manage-nems-subscription-repository-report.json.zip
|
27.3 KB |
sha256:2124f6cf79e119b289ac23ff89b9ad7a5c7aaba365065e9a3b914a8b6288f977
|
|
|
vulnerabilities-manage-participant-repository-report.json.zip
|
27.3 KB |
sha256:ec61a660b4c58d735306d6954d40b50c1d01d164bda47090903c74776cb52b11
|
|
|
vulnerabilities-manage-servicenow-participant-repository-report.json.zip
|
27.4 KB |
sha256:06b054c3fe90585187d04631d4050d776c281d3c82c836b836fbd967edc88251
|
|
|
vulnerabilities-nems-mesh-retrieval-repository-report.json.zip
|
27.3 KB |
sha256:82cab0d2bde3e0e7ab67af5dc29bf450dfd0be9bbf01476ea645ea058b7d65cd
|
|
|
vulnerabilities-nems-subscription-data-service-repository-report.json.zip
|
27.4 KB |
sha256:33ef65bafc07ffc5674c9b510182b82134f6337d8819bd6101a0b1a39fe689da
|
|
|
vulnerabilities-participant-demographic-data-service-repository-report.json.zip
|
27.4 KB |
sha256:1fa0dd32355dae7ce96c8f64441489adbd0a303bfc6391c98baea941f64d0b67
|
|
|
vulnerabilities-participant-management-data-service-repository-report.json.zip
|
27.4 KB |
sha256:9e9cdc21aa476a18f751aeae2f9f3d3bc73bf0ddabbd586f65c423de98fb8db4
|
|
|
vulnerabilities-process-nems-update-repository-report.json.zip
|
27.3 KB |
sha256:fbbd28023235a8f5c250253500bd61b81ac0bf6a1a7270112bf969ae18a76359
|
|
|
vulnerabilities-receive-caas-file-repository-report.json.zip
|
27.3 KB |
sha256:3c8e64aaaba9df5365b7bb3d164efd00bdb89d01e592999d955ace76cfacae2c
|
|
|
vulnerabilities-reference-data-service-repository-report.json.zip
|
27.3 KB |
sha256:ba1b425692227392ce800d82bb5169540a003e5daac6f66e2cb90631e608c422
|
|
|
vulnerabilities-remove-dummy-gp-code-repository-report.json.zip
|
27.3 KB |
sha256:bb1e42c4cc8e1560a4b4c189a8d3daf64167f1034e5c4323c429ea0e65847839
|
|
|
vulnerabilities-remove-validation-exception-data-repository-report.json.zip
|
27.4 KB |
sha256:b70b1ae82ec62f94dfd03db958086c1e206662dbb817153208a0d5d7ab604974
|
|
|
vulnerabilities-retrieve-cohort-distribution-data-repository-report.json.zip
|
27.4 KB |
sha256:219815306d562dabe8cd038cc1197366801f21ad477edb79ace43274fd3ebd2c
|
|
|
vulnerabilities-retrieve-cohort-request-audit-repository-report.json.zip
|
27.3 KB |
sha256:8404c1a118739c6fa6bc2b38244d542e139fdbe028ddf23783f654892fc7d5dd
|
|
|
vulnerabilities-retrieve-mesh-file-repository-report.json.zip
|
27.3 KB |
sha256:1641cd2b01c768f9930ee80394f43d9784d93613a2a5ec7f8940733c821b0253
|
|
|
vulnerabilities-retrieve-pds-demographic-repository-report.json.zip
|
27.3 KB |
sha256:5e8fb9859e43a1de63aca7ef00b3b3a1e135c7da16c3aa4c0e6dde930286fada
|
|
|
vulnerabilities-screening-lkp-data-service-repository-report.json.zip
|
27.4 KB |
sha256:842bc7b13284c24c996d60940174a320333fed3d52a2e3c492bc0f3d7eff903b
|
|
|
vulnerabilities-servicenow-cases-data-service-repository-report.json.zip
|
27.4 KB |
sha256:3cf512e31f8c66ca747ae02e60bd6a0378cc3624337b47aab227124778282787
|
|
|
vulnerabilities-servicenow-cohort-lookup-repository-report.json.zip
|
27.3 KB |
sha256:bd473d6db54ad7eba83fe6ec46cd306dfdb83f9f35daaa06c1b4afad94874020
|
|
|
vulnerabilities-servicenow-message-handler-repository-report.json.zip
|
27.3 KB |
sha256:116dfee8a4319f375d5b40cc0e6ae7854771bbaed84d9e0c238b305ed15237f5
|
|
|
vulnerabilities-static-validation-repository-report.json.zip
|
27.3 KB |
sha256:02a175ec29bd55e21a2be01a82db41d7141038d140df0e2d046bcccc3ba82ebe
|
|
|
vulnerabilities-transform-data-service-repository-report.json.zip
|
27.3 KB |
sha256:86afa232b22ae65696161c60d0f7dc0851d1fe18eb0f4b0f1914109491b4b79c
|
|
|
vulnerabilities-update-blocked-flag-repository-report.json.zip
|
27.3 KB |
sha256:e3ab4476895e3be93f078d697e78b4f0b1d8c5bae28c6dd55cab23b3c5d24efb
|
|
|
vulnerabilities-update-exception-repository-report.json.zip
|
27.3 KB |
sha256:bed8793ca9783861309d3f9c0bc6c7f4851e63f3dd38a7ef322ad1bc38cb7d9c
|
|
|
vulnerabilities-web-repository-report.json.zip
|
27.3 KB |
sha256:e846e068d522508ddea80aed34160f7feb22e52ac6aa6592963772e28c3ebf02
|
|
|
vulnerabilities-wiremock-repository-report.json.zip
|
27.3 KB |
sha256:e58adac1ecd97e1348b8ad499cadf72a9a6b1726ddfd3907b1efaaef0f531fd8
|
|