container-scanning version 7.3.4 image panics on startup

Summary

The container-scanning analyzer fails to run on invocation with a panic message.

Steps to reproduce

1. Run docker run --rm -it registry.gitlab.com/security-products/container-scanning:7 gtcs
2. Observe panic message

Example Project

What is the current bug behavior?

The analyzer immediately panics, and exits.

What is the expected correct behavior?

The scans launches successfully as expected.

Relevant logs and/or screenshots

<internal:/usr/local/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:136:in `require': cannot load such file -- mize (LoadError)
        from <internal:/usr/local/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:136:in `require'
        from /usr/local/bundle/gems/zeitwerk-2.6.17/lib/zeitwerk/kernel.rb:34:in `require'
        from /usr/local/bundle/gems/term-ansicolor-1.11.1/lib/term/ansicolor.rb:3:in `<top (required)>'
        from <internal:/usr/local/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:136:in `require'
        from <internal:/usr/local/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:136:in `require'
        from /usr/local/bundle/gems/zeitwerk-2.6.17/lib/zeitwerk/kernel.rb:34:in `require'
        from /usr/local/bundle/gems/gcs-7.3.4/lib/gcs.rb:18:in `<top (required)>'
        from <internal:/usr/local/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:136:in `require'
        from <internal:/usr/local/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:136:in `require'
        from /usr/local/bundle/gems/gcs-7.3.4/exe/gtcs:4:in `<top (required)>'
        from /usr/local/bundle/bin/gtcs:25:in `load'
        from /usr/local/bundle/bin/gtcs:25:in `<main>'

Possible fixes

• Pin container-scanning image to version 7.3.3:

include:
  - template: Jobs/Container-Scanning.gitlab-ci.yml

container_scanning:
  variables:
    CS_ANALYZER_IMAGE: "$CI_TEMPLATE_REGISTRY_HOST/security-products/container-scanning:7.3.3"