Skip to content

refactor: rename os-image-composer to ICT across entire codebase #443

refactor: rename os-image-composer to ICT across entire codebase

refactor: rename os-image-composer to ICT across entire codebase #443

Triggered via pull request April 21, 2026 06:01
Status Success
Total duration 2m 12s
Artifacts 4

pre-merge.yml

on: pull_request
pre-merge  /  sanitize-project-folder
3s
pre-merge / sanitize-project-folder
pre-merge  /  license-compliance-check
0s
pre-merge / license-compliance-check
pre-merge  /  run-repo-pipelines
1m 40s
pre-merge / run-repo-pipelines
pre-merge  /  zizmor-scan
11s
pre-merge / zizmor-scan
pre-merge  /  secrets-gitleaks-scan
13s
pre-merge / secrets-gitleaks-scan
pre-merge  /  trivy-filesystem-scan
14s
pre-merge / trivy-filesystem-scan
pre-merge  /  trivy-critical-scan
12s
pre-merge / trivy-critical-scan
pre-merge  /  trivy-config-scan
14s
pre-merge / trivy-config-scan
pre-merge  /  bandit
12s
pre-merge / bandit
Matrix: pre-merge / Scan Docker Images for CIS
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
pre-merge / zizmor-scan
No file matched to [/home/runner/work/image-composer-tool/image-composer-tool/**/*requirements*.txt,/home/runner/work/image-composer-tool/image-composer-tool/**/*requirements*.in,/home/runner/work/image-composer-tool/image-composer-tool/**/*constraints*.txt,/home/runner/work/image-composer-tool/image-composer-tool/**/*constraints*.in,/home/runner/work/image-composer-tool/image-composer-tool/**/pyproject.toml,/home/runner/work/image-composer-tool/image-composer-tool/**/uv.lock,/home/runner/work/image-composer-tool/image-composer-tool/**/*.py.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
pre-merge / trivy-critical-scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. 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/
pre-merge / secrets-gitleaks-scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. 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/
pre-merge / trivy-filesystem-scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. 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/
pre-merge / trivy-config-scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. 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
gitleaks-results-k7xnv3-image-composer-tool
175 Bytes
sha256:22532f215927e282cffbd87b9ed7c1ebbac0f518a13fa17c4f0757c32bb7d5ff
trivy-config-scan-image-composer-tool
496 Bytes
sha256:7e00753ef1331350ebe7835b44d2e8631d8de3839037aac1abfe2c0c688bc5fe
trivy-fs-scan-report-image-composer-tool
1.29 KB
sha256:198aaaf9cc183ed1ad397ab0ff1b9668b17916c4c58dd6a60291feb6186a224c
zizmor-scan-report-image-composer-tool
594 Bytes
sha256:03d325e7303936285982168fd1fd0125a91f2ef3f26b202fce3b61db4d2f7264