Update to new containers #3985
kkanasuniversalnrp-test.yml
on: pull_request
Annotations
58 warnings
|
Package / package
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/
|
|
MC Test (debian, 12, amd64, Audit, LinuxSshServerSecurityBaseline, SSH, 20)
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/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/
|
|
MC Test (debian, 11, amd64, Audit, AzureLinuxBaseline, ASB, 169)
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/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/
|
|
Module Test (almalinux, 9, amd64)
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/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/
|
|
MC Test (ubuntu, 24.04, amd64, Audit, LinuxSshServerSecurityBaseline, SSH, 20)
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/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/
|
|
MC Test (debian, 11, amd64, Audit, LinuxSshServerSecurityBaseline, SSH, 20)
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/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/
|
|
MC Test (ubuntu, 24.04, amd64, Audit, AzureLinuxBaseline, ASB, 169)
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/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/
|
|
MC Test (ubuntu, 20.04, amd64, Audit, AzureLinuxBaseline, ASB, 169)
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/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/
|
|
Module Test (rhel, 9, amd64)
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/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/
|
|
MC Test (ubuntu, 20.04, amd64, Audit, LinuxSshServerSecurityBaseline, SSH, 20)
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/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/
|
|
MC Test (almalinux, 9, amd64, Audit, AzureLinuxBaseline, ASB, 169)
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/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/
|
|
MC Test (almalinux, 9, amd64, Audit, LinuxSshServerSecurityBaseline, SSH, 20)
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/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/
|
|
MC Test (ubuntu, 22.04, amd64, Audit, LinuxSshServerSecurityBaseline, SSH, 20)
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/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/
|
|
MC Test (rhel, 9, amd64, Audit, LinuxSshServerSecurityBaseline, SSH, 20)
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/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/
|
|
MC Test (rhel, 9, amd64, Audit, AzureLinuxBaseline, ASB, 169)
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/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/
|
|
MC Test (ubuntu, 22.04, amd64, Audit, AzureLinuxBaseline, ASB, 169)
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/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/
|
|
MC Test (debian, 11, amd64, Remediate, LinuxSshServerSecurityBaseline, SSH, 20)
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/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/
|
|
MC Test (debian, 12, amd64, Audit, AzureLinuxBaseline, ASB, 169)
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/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/
|
|
MC Test (ubuntu, 24.04, amd64, Remediate, LinuxSshServerSecurityBaseline, SSH, 20)
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/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/
|
|
MC Test (debian, 11, amd64, Remediate, AzureLinuxBaseline, ASB, 169)
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/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/
|
|
MC Test (almalinux, 9, amd64, Remediate, LinuxSshServerSecurityBaseline, SSH, 20)
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/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/
|
|
MC Test (ubuntu, 20.04, amd64, Remediate, LinuxSshServerSecurityBaseline, SSH, 20)
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/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/
|
|
MC Test (rhel, 9, amd64, Remediate, LinuxSshServerSecurityBaseline, SSH, 20)
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/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/
|
|
MC Test (debian, 12, amd64, Remediate, LinuxSshServerSecurityBaseline, SSH, 20)
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/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/
|
|
MC Test (ubuntu, 24.04, amd64, Remediate, AzureLinuxBaseline, ASB, 169)
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/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/
|
|
MC Test (ubuntu, 22.04, amd64, Remediate, LinuxSshServerSecurityBaseline, SSH, 20)
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/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/
|
|
MC Test (ubuntu, 20.04, amd64, Remediate, AzureLinuxBaseline, ASB, 169)
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/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/
|
|
MC Test (debian, 12, amd64, Remediate, AzureLinuxBaseline, ASB, 169)
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/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/
|
|
MC Test (almalinux, 9, amd64, Remediate, AzureLinuxBaseline, ASB, 169)
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/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/
|
|
MC Test (rhel, 9, amd64, Remediate, AzureLinuxBaseline, ASB, 169)
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/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/
|
|
MC Test (oraclelinux, 8, amd64, Audit, AzureLinuxBaseline, ASB, 169)
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/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/
|
|
MC Test (rhel, 8, amd64, Audit, LinuxSshServerSecurityBaseline, SSH, 20)
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/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/
|
|
MC Test (rhel, 8, amd64, Audit, AzureLinuxBaseline, ASB, 169)
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/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/
|
|
MC Test (ubuntu, 22.04, amd64, Remediate, AzureLinuxBaseline, ASB, 169)
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/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/
|
|
MC Test (oraclelinux, 8, amd64, Audit, LinuxSshServerSecurityBaseline, SSH, 20)
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/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/
|
|
MC Test (oraclelinux, 8, amd64, Remediate, LinuxSshServerSecurityBaseline, SSH, 20)
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/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/
|
|
MC Test (rhel, 8, amd64, Remediate, LinuxSshServerSecurityBaseline, SSH, 20)
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/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/
|
|
Module Test (azurelinux, 3, amd64)
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/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/
|
|
Module Test (sles, 15, amd64)
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/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/
|
|
Module Test (oraclelinux, 8, amd64)
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/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/
|
|
MC Test (sles, 15, amd64, Audit, LinuxSshServerSecurityBaseline, SSH, 20)
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/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/
|
|
MC Test (sles, 15, amd64, Audit, AzureLinuxBaseline, ASB, 169)
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/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/
|
|
Module Test (rhel, 8, amd64)
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/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/
|
|
MC Test (azurelinux, 3, amd64, Audit, AzureLinuxBaseline, ASB, 169)
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/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/
|
|
MC Test (azurelinux, 3, amd64, Audit, LinuxSshServerSecurityBaseline, SSH, 20)
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/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/
|
|
MC Test (oraclelinux, 8, amd64, Remediate, AzureLinuxBaseline, ASB, 169)
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/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/
|
|
MC Test (sles, 15, amd64, Remediate, LinuxSshServerSecurityBaseline, SSH, 20)
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/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/
|
|
MC Test (azurelinux, 3, amd64, Remediate, AzureLinuxBaseline, ASB, 169)
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/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/
|
|
Module Test (debian, 11, amd64)
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/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/
|
|
MC Test (sles, 15, amd64, Remediate, AzureLinuxBaseline, ASB, 169)
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/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/
|
|
Module Test (debian, 12, amd64)
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/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/
|
|
MC Test (rhel, 8, amd64, Remediate, AzureLinuxBaseline, ASB, 169)
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/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/
|
|
MC Test (azurelinux, 3, amd64, Remediate, LinuxSshServerSecurityBaseline, SSH, 20)
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/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/
|
|
Module Test (ubuntu, 20.04, amd64)
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/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/
|
|
Module Test (ubuntu, 24.04, amd64)
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/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/
|
|
Module Test (ubuntu, 22.04, amd64)
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/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/
|
|
Local Tests
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/upload-artifact@v4, azure/login@v2. 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/
|
|
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 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 | |
|---|---|---|---|
|
almalinux-9_ASB-Audit_logs
|
46.2 KB |
sha256:319a6f5c9ad316f3a6d745a92fa852d3eb7b0658417c263aac6b417ee473da56
|
|
|
almalinux-9_ASB-Audit_report
|
815 Bytes |
sha256:009e87d326f3ed6153a7131e373580499334ee6902950e97d9ccae1584567083
|
|
|
almalinux-9_ASB-Remediate_logs
|
119 KB |
sha256:4c66c957c154392a53346f85d4af2d37895e7efc81f901d262b6c119e89cbbf6
|
|
|
almalinux-9_ASB-Remediate_report
|
791 Bytes |
sha256:3d50da14d5bc753f5ca372a05773b1b6281bbca2877209d95cf9cce65ae6cf0e
|
|
|
almalinux-9_SSH-Audit_logs
|
8.87 KB |
sha256:1b5417dbbc33fb31fe9270a3751621d508f97df6c024960feb15b97105239e2b
|
|
|
almalinux-9_SSH-Audit_report
|
810 Bytes |
sha256:d7f6506ce387f5e42af67cb33111f825ff4f720e7b07ade8713331f91661eace
|
|
|
almalinux-9_SSH-Remediate_logs
|
20 KB |
sha256:ac582e43ee1392f64badda1cb030575b38f00ebcb7fbb141d36b328b5879253a
|
|
|
almalinux-9_SSH-Remediate_report
|
794 Bytes |
sha256:9fc2d79e388c46592e348d5d86dc6a6344d91da7d62ba0a83188651cffe905d7
|
|
|
almalinux-9_logs
|
46.6 KB |
sha256:f1c9b78eeb88f2f343b1b455f0b40eb1ff683e5e388947d710855d196b4900ea
|
|
|
azurelinux-3_ASB-Audit_logs
|
45.3 KB |
sha256:4082984843c33f182e69b3050ec7b386c042bd9dc9ebaa14e367ef63e28c92ec
|
|
|
azurelinux-3_ASB-Audit_report
|
808 Bytes |
sha256:0806a4bc198dc486b445d8414c751e456166d1a8d2d41ffe16e935abfb72527c
|
|
|
azurelinux-3_ASB-Remediate_logs
|
114 KB |
sha256:9db75d9ae9922c3e24364bc5f0c25fdfe75d93247053823a3ca1687c419c8006
|
|
|
azurelinux-3_ASB-Remediate_report
|
790 Bytes |
sha256:70ed6af0dfc689f15f3f12dff377107eea82ad9991e8fd4a79975755e0f22971
|
|
|
azurelinux-3_SSH-Audit_logs
|
8.52 KB |
sha256:f98c19ff33f1f88161375830c976fc21f43be13132d4ad7f1c5d42e46563346e
|
|
|
azurelinux-3_SSH-Audit_report
|
807 Bytes |
sha256:17a7aaebc845587d13cd24e698f5a51e4087735ea2efc90036f6e980a44bad7c
|
|
|
azurelinux-3_SSH-Remediate_logs
|
18.7 KB |
sha256:305e81b08d98ca6886699c05109a259e19526fb8e8f70a73ff76243244ff0466
|
|
|
azurelinux-3_SSH-Remediate_report
|
787 Bytes |
sha256:8fabdd82a92f49b9814cab0fe1b367a98298416d53996f066afe9b420a4a5aef
|
|
|
azurelinux-3_logs
|
45.1 KB |
sha256:b8a8611b1c4424f2bc87896832e9aa30bf45e660f81784f4dbe14d670ca61d8a
|
|
|
debian-11_ASB-Audit_logs
|
46.2 KB |
sha256:0ca59c38f896ccf9a7ce1ef944a38cd9f9a3d87c937f73774d3a9893db326f44
|
|
|
debian-11_ASB-Audit_report
|
804 Bytes |
sha256:00f3a91ae7a5664b0d2a5efa78b1c2f19ce60d609f6fda43711bf731ace449c2
|
|
|
debian-11_ASB-Remediate_logs
|
118 KB |
sha256:271d9414aa947875a69e7cc99be7989817040c4668fb725bddec38e500d03fc5
|
|
|
debian-11_ASB-Remediate_report
|
787 Bytes |
sha256:f367cd0051482126e0bdbe4cf6d7c5e5464f8c03d0fd7cb01b9dce5dcaf45e18
|
|
|
debian-11_SSH-Audit_logs
|
8.81 KB |
sha256:b0e1f4d81fc5ea4ec2670a5c5596f25e96e30552c91f4768b9a462f80f6a76d2
|
|
|
debian-11_SSH-Audit_report
|
803 Bytes |
sha256:278edbeba2ebbed6c6e27ae8bf98e7518735d9fa6c6a54584779baa32266d977
|
|
|
debian-11_SSH-Remediate_logs
|
20 KB |
sha256:733b3ef90752c67be2e751c5f446e1a45a7aeb535b33af3078fdd0e04b621425
|
|
|
debian-11_SSH-Remediate_report
|
787 Bytes |
sha256:c20b40249dd9f1918c42c9f9635e5795bd46f478eb1e213d0002e98bf6b07260
|
|
|
debian-11_logs
|
45.2 KB |
sha256:0d066fb62ad601b42e1d491db30658b2d9dc8328f98f716f66eee9af0d489cb4
|
|
|
debian-12_ASB-Audit_logs
|
45.4 KB |
sha256:e464d0df694127b0232211e8350f101fa159c5db0f6710cc4f1ac8348859a0c9
|
|
|
debian-12_ASB-Audit_report
|
804 Bytes |
sha256:b8abb84bc856858cb7eced6f92f3181c68f95c0700c383c18f53eff8e1f6283d
|
|
|
debian-12_ASB-Remediate_logs
|
118 KB |
sha256:5e3d3bc9cddeb963b9eb0242df079a29b0482442eaa2637d2e40e1578788c6b2
|
|
|
debian-12_ASB-Remediate_report
|
780 Bytes |
sha256:91420d379b839a3301046e8bc623d57d059441e5e85c9eb8c9e79bc99b1833ec
|
|
|
debian-12_SSH-Audit_logs
|
8.67 KB |
sha256:53b8197e709025c76df61f7f6f30dd538e7c45237fa47f4b085d7037358072dc
|
|
|
debian-12_SSH-Audit_report
|
804 Bytes |
sha256:8fcace5ad6cf8e4ad72c2954cce2c16f84def9e069fa796d0e89ff987282b78a
|
|
|
debian-12_SSH-Remediate_logs
|
19.6 KB |
sha256:446628f9a73eecccdf28ad8ab034864a53b45bb628f677c2a1455a05ff667a7b
|
|
|
debian-12_SSH-Remediate_report
|
780 Bytes |
sha256:03fce7d901c582b9dead2716acc4de1ca3a74d4bab373bc0e891aae23c3abfab
|
|
|
debian-12_logs
|
45.5 KB |
sha256:ebca382d0d0dae28a6f468d972d166b180a12a6689af1af358a65cdaa5dacf9b
|
|
|
local_tests_logs
|
1.41 MB |
sha256:ee43b995ee40c695a21e1eb92f9498b96a564c778ec9fca3c8585bba1d78c970
|
|
|
local_tests_reports
|
15.8 KB |
sha256:80dd54387870e0503b33977cb6cce8c2240cbb8945e93e21c5a5e0bd0b2502ad
|
|
|
nrp-test
|
29.2 MB |
sha256:cc959d163f146f0c7e48655ba999cd824b71419a276e531248b0da8cb4040aa5
|
|
|
oraclelinux-8_ASB-Audit_logs
|
47.1 KB |
sha256:6e2122c89ce72bfdb49faa093329ad1c89047e9f7e6764134a913af19c4aaf8e
|
|
|
oraclelinux-8_ASB-Audit_report
|
823 Bytes |
sha256:4882d5675a8fd749740909ffba75df350ea12a8aad5db2cd402b80e3b1164383
|
|
|
oraclelinux-8_ASB-Remediate_logs
|
121 KB |
sha256:7f0620a1839a2abc3369d7cfa7511ac56209ecebd1114b1658681c7721aa4b7e
|
|
|
oraclelinux-8_ASB-Remediate_report
|
801 Bytes |
sha256:177fafdad8ba8ef05cc598a277436dec3bbc406705bcd50c95a17f3140d749e2
|
|
|
oraclelinux-8_SSH-Audit_logs
|
8.8 KB |
sha256:c410291378b75bbb6ac55c1d4a0fa8a1a830e408cf463105958eafabd183e453
|
|
|
oraclelinux-8_SSH-Audit_report
|
818 Bytes |
sha256:ac0b44634eec9f8435b5544bfda7019f0024d834fdf57f8121fe88ee8a534625
|
|
|
oraclelinux-8_SSH-Remediate_logs
|
19.4 KB |
sha256:f0864f50b52fcd2ddfd1c4365af893d57763ce08c2f19c9a35a33cd562ae641b
|
|
|
oraclelinux-8_SSH-Remediate_report
|
801 Bytes |
sha256:7f482bda95a442418c783b7deab6ef0bb994424ad8f3cb7f6b6c7b9b1a53b6be
|
|
|
oraclelinux-8_logs
|
47.3 KB |
sha256:967d773a30ea304c12a7a30e585d9eb43595f9bd2620ee2531d49cca2005b665
|
|
|
rhel-8_ASB-Audit_logs
|
46.5 KB |
sha256:747c55b52f7ca20bd9bcfa57ef92638e846ff47638e7dec4f8b3ea85ff1f0307
|
|
|
rhel-8_ASB-Audit_report
|
809 Bytes |
sha256:38bc6633901b55e15abdf80a0e5325eaea5bebbe1b00b6c5c0044206bf002120
|
|
|
rhel-8_ASB-Remediate_logs
|
120 KB |
sha256:736962b85f78316ed8777ec9c2e4e389c9cf91d911c49469debebfe53d1d9454
|
|
|
rhel-8_ASB-Remediate_report
|
787 Bytes |
sha256:32dd4b06eea6edcd0caef19b7ace2b81ee82ad08348aee6da2e4299777232201
|
|
|
rhel-8_SSH-Audit_logs
|
8.82 KB |
sha256:c3212df9a8e915e0349ad8095b16afff0c815ceb680886a612a30e65aba2e4ae
|
|
|
rhel-8_SSH-Audit_report
|
803 Bytes |
sha256:4427da8e17888f5ddd85fc8dc0c858f7546dc948ec7914a135e1c2121a683138
|
|
|
rhel-8_SSH-Remediate_logs
|
19.6 KB |
sha256:df3b53024978d6c648499dd937c37298f009a024ce3250e0ab2743e0aed0f9d4
|
|
|
rhel-8_SSH-Remediate_report
|
787 Bytes |
sha256:80e5fa8cd6ce66f24f036c3be031030261262a8cf9251d023d3484e9d6da3916
|
|
|
rhel-8_logs
|
46.9 KB |
sha256:a5e2781ab9c1e4e9286d84ddf3dd5f927b295038908eea4e53be6587fc1d111f
|
|
|
rhel-9_ASB-Audit_logs
|
46.4 KB |
sha256:4caa38163cfd6aec735c972268c86280037e940d5e11a7b1a6f0dbef5b552097
|
|
|
rhel-9_ASB-Audit_report
|
805 Bytes |
sha256:1d7609e47033c7e1a4361952beafd0d387153cea7eb781195bc22eae8ea141f0
|
|
|
rhel-9_ASB-Remediate_logs
|
120 KB |
sha256:297f2ba1db269ff17cbcdb7098c30cb5e5cb80fdbe6a513afbcf9e73c798589a
|
|
|
rhel-9_ASB-Remediate_report
|
787 Bytes |
sha256:ad5e335b2fc575bdd3a1530059b1b3fd9f73f73804d2592bbe52769cf09836a9
|
|
|
rhel-9_SSH-Audit_logs
|
9.05 KB |
sha256:a7a9b0c6faef30b6ab8867d464db4683ea470c0afdc33851b00ba9a15078a0e9
|
|
|
rhel-9_SSH-Audit_report
|
806 Bytes |
sha256:42932207080e2f0cbf5936cd5449a99abdf5c9a33809a81ddc7332520ab56e81
|
|
|
rhel-9_SSH-Remediate_logs
|
20.1 KB |
sha256:2818d423b862192b2fbba2c06b59303de4b16f7dd1f5eb7747a3b9de4fa20f04
|
|
|
rhel-9_SSH-Remediate_report
|
785 Bytes |
sha256:5ccdc9946b0496c70ef6e03681a1e7cc61443480006b06c5531cbb347c017869
|
|
|
rhel-9_logs
|
46.5 KB |
sha256:a72349aef263c5cf3e5f02efed6da4bfec912a33972dd07aa3bfcedee7fcd583
|
|
|
sles-15_ASB-Audit_logs
|
46.3 KB |
sha256:56381d9aed155afc05e3aa9b3e7e57a335d53a0c81249213df702373cc7531b9
|
|
|
sles-15_ASB-Audit_report
|
805 Bytes |
sha256:0a6d0f25ee8498d18aa999d92ce288c2a6e911d6f90980335830e9e530223ab6
|
|
|
sles-15_ASB-Remediate_logs
|
119 KB |
sha256:78c3e8542e3f760558202b589f9b2d52df0e8ab063de638d71b5af992c53cac6
|
|
|
sles-15_ASB-Remediate_report
|
784 Bytes |
sha256:64e4cbb95e31341fdf938abed24ace1644ae9ef35e3c758180faee16467f4160
|
|
|
sles-15_SSH-Audit_logs
|
8.95 KB |
sha256:2352ebd3785c81feb0ed25a057fa0c3c43d181864e6de67887b902c57cd2daca
|
|
|
sles-15_SSH-Audit_report
|
804 Bytes |
sha256:195311c5d5b74a6b9f93d15165aea4718b665ead45f65f9a6743a874d0761ab8
|
|
|
sles-15_SSH-Remediate_logs
|
20 KB |
sha256:742376f600d9bfe13699f2c16cbc53a565550d1851600671bd36aac34c1b6d00
|
|
|
sles-15_SSH-Remediate_report
|
787 Bytes |
sha256:3660afc61bbda8e1d321b530c69b16b579e44986fe83678c094ef25b281839f3
|
|
|
sles-15_logs
|
45.8 KB |
sha256:18c17e58abe7b662f71c2c6243466591c722f3c88ac1a36cdabecab505843d56
|
|
|
ubuntu-20.04_ASB-Audit_logs
|
47.3 KB |
sha256:ab6f95e7eadb95cbb641ec2b7041a8a7c379e608253339bddfa730c0e584ecd7
|
|
|
ubuntu-20.04_ASB-Audit_report
|
803 Bytes |
sha256:20023b24489a9c2ee725798c781106cf13876d3fc10bf22b342638b767bb625c
|
|
|
ubuntu-20.04_ASB-Remediate_logs
|
121 KB |
sha256:62c9e2a6ebf2e2cfb79f491ff338548e153295c7521a70ef025a1ce3f0b8848c
|
|
|
ubuntu-20.04_ASB-Remediate_report
|
784 Bytes |
sha256:788796fd39e88120ab2ccaeb7b2a9d2868ebfffa78dc0f98f6cb3622c7d5e849
|
|
|
ubuntu-20.04_SSH-Audit_logs
|
8.95 KB |
sha256:6fabc3e6fcfacc48618892fbfe6e0dba5b79d00b4dddddc34c54ceb66a86c39c
|
|
|
ubuntu-20.04_SSH-Audit_report
|
803 Bytes |
sha256:d130ba7e1b38673fdd83ed7643eb40f1b83f50c9803cdec73f0d7b15ce668294
|
|
|
ubuntu-20.04_SSH-Remediate_logs
|
20.1 KB |
sha256:433f44c2a04d52e6d743e03e1144a02659a73793deffbc2935e85ed90bc8ded9
|
|
|
ubuntu-20.04_SSH-Remediate_report
|
785 Bytes |
sha256:855a6f5d61ee6b1c11ccc179c07a3b8866134878eba558afc1c7a3e1eb2f305c
|
|
|
ubuntu-20.04_logs
|
45.9 KB |
sha256:eed9d4ee21a42c2ca8cedeb664ff3cbdf5edfb3192a4396a56583f91f7bd2547
|
|
|
ubuntu-22.04_ASB-Audit_logs
|
47.4 KB |
sha256:e3bbb056ffbce377bcc6a2db8a3791d5e123c32521a5be09d322801c3ba9992d
|
|
|
ubuntu-22.04_ASB-Audit_report
|
808 Bytes |
sha256:7a7dd5fdec939c662af4ff487e1e1df98cf9d0cea8cc70d5589cec20cca4cc17
|
|
|
ubuntu-22.04_ASB-Remediate_logs
|
119 KB |
sha256:5c4aa0904e6adc3609c6e0cbf8b5d3930f6630c914fd85082ac55c7130856c20
|
|
|
ubuntu-22.04_ASB-Remediate_report
|
790 Bytes |
sha256:991b92d0cb1dc3be666dbee9484ba1448647a124b50ef283d1a030582bc75df3
|
|
|
ubuntu-22.04_SSH-Audit_logs
|
8.9 KB |
sha256:e747832655c547b79f0b7c84193fd1e4ef32bd172e9facf3a94db6f3b9f1a5b6
|
|
|
ubuntu-22.04_SSH-Audit_report
|
803 Bytes |
sha256:b24bab7fcd8757348c91762f293899d00de5a72530e6f95192370733df023370
|
|
|
ubuntu-22.04_SSH-Remediate_logs
|
20 KB |
sha256:cf534cc0d098365bdc030bd3a24bf1218573ac170595d377dadb2618b1f22bac
|
|
|
ubuntu-22.04_SSH-Remediate_report
|
788 Bytes |
sha256:85e837bc69c14b8455078fc91931829826c05afcc636f1470e84480d7918fa6a
|
|
|
ubuntu-22.04_logs
|
45.5 KB |
sha256:148701ef49d700515bec31a6cc3158a6e0068b382767d3ea0a78efff12a0408b
|
|
|
ubuntu-24.04_ASB-Audit_logs
|
44.5 KB |
sha256:4180a75528e85c544a23e7cac5ece96be3e1e176a1367a9ed0950e95bba1ec11
|
|
|
ubuntu-24.04_ASB-Audit_report
|
805 Bytes |
sha256:72dfa03d3f9d35569cd4ed2515500f820c922d7edb404fcb71428ae6df100c12
|
|
|
ubuntu-24.04_ASB-Remediate_logs
|
114 KB |
sha256:8f19ee12ea53e5ce69eb3f66ebd9efe938a48c5d1b55d65230f5a9b361b85a4d
|
|
|
ubuntu-24.04_ASB-Remediate_report
|
788 Bytes |
sha256:1c8a95617959f0f0e8545b6556dc2c0877884a4c2945feae256ff18085a97ac6
|
|
|
ubuntu-24.04_SSH-Audit_logs
|
6.46 KB |
sha256:9b2bc404ee3c45b0b1aa3c05570234b295424d5f4b305246016126524a8552ef
|
|
|
ubuntu-24.04_SSH-Audit_report
|
802 Bytes |
sha256:98902952fe54db2e9ac544efb4700bdf3af8b6f6b30dfc5f1dfbf29dc88a8790
|
|
|
ubuntu-24.04_SSH-Remediate_logs
|
13.8 KB |
sha256:3bcdec7e6df46e89d1efcdc79e869f881b338dd230864c8699a7f3dde6b248a6
|
|
|
ubuntu-24.04_SSH-Remediate_report
|
788 Bytes |
sha256:cb4d0cb9b496a54c38250e147fbf3c429045566814d4db6aad19c8ed81a0c8a7
|
|
|
ubuntu-24.04_logs
|
44.9 KB |
sha256:c10131719d9042c4af74dbb6fa5516b026043a6a5dd2181ddecd85448245ed12
|
|