Secret detection fails with exit status 128

Summary

Using the secret detection fails with error 128.

Steps to reproduce

1. Use:

include:
  - template: Security/Secret-Detection.gitlab-ci.yml

variables:
  SECURE_LOG_LEVEL: "debug"

stages:
  - test

test1:
  stage: test
  script:
    - echo "Do a test here"

2. Run the CI pipeline

Example Project

TBD

What is the current bug behavior?

$ /analyzer run
[INFO] [secrets] [2022-05-27T07:01:17Z] ▶ GitLab secrets analyzer v4.0.1
[INFO] [secrets] [2022-05-27T07:01:17Z] ▶ Detecting project
[INFO] [secrets] [2022-05-27T07:01:17Z] ▶ Found relevant files in project, analyzing entire repository
[INFO] [secrets] [2022-05-27T07:01:17Z] ▶ Running analyzer
[DEBU] [secrets] [2022-05-27T07:01:17Z] ▶ custom rulesets not enabled
exit status 128

The exit status 128 is returned.

What is the expected correct behavior?

secrets analyzer finishes without issues

Relevant logs and/or screenshots

Output of checks

This bug happens on GitLab.com

Results of GitLab environment info

Expand for output related to GitLab environment info

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)
(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)
(we will only investigate if the tests are passing)

Possible fixes