chore(deps): updated recruit chart to 10.4.5

[miracum-bot]

Automated changes by create-pull-request GitHub action

[github-actions]

✅MegaLinter analysis: Success

Descriptor	Linter	Files	Fixed	Errors	Warnings	Elapsed time
✅ ACTION	actionlint	4		0	0	0.12s
✅ BASH	bash-exec	5		0	0	0.02s
✅ BASH	shellcheck	5		0	0	0.14s
✅ BASH	shfmt	5		0	0	0.0s
✅ EDITORCONFIG	editorconfig-checker	265		0	0	0.38s
✅ JSON	jsonlint	2		0	0	0.27s
✅ JSON	prettier	2		0	0	0.77s
✅ MARKDOWN	markdownlint	15		0	0	2.27s
✅ REPOSITORY	checkov	yes		no	no	29.75s
✅ REPOSITORY	dustilock	yes		no	no	0.04s
✅ REPOSITORY	gitleaks	yes		no	no	1.24s
✅ REPOSITORY	git_diff	yes		no	no	0.02s
✅ REPOSITORY	grype	yes		no	no	42.7s
✅ REPOSITORY	secretlint	yes		no	no	2.8s
✅ REPOSITORY	syft	yes		no	no	2.16s
✅ REPOSITORY	trivy	yes		no	no	11.42s
✅ REPOSITORY	trivy-sbom	yes		no	no	0.23s
✅ REPOSITORY	trufflehog	yes		no	no	3.81s
✅ YAML	prettier	177		0	0	1.76s
✅ YAML	yamllint	177		0	0	7.52s

See detailed reports in MegaLinter artifacts

You could have the same capabilities but better runtime performances if you use a MegaLinter flavor:

• oxsecurity/megalinter/flavors/documentation@v9.4.0 (51 linters)
• oxsecurity/megalinter/flavors/ruby@v9.4.0 (52 linters)
• oxsecurity/megalinter/flavors/rust@v9.4.0 (52 linters)

Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining FLAVOR_SUGGESTIONS: false)

• Documentation: Custom Flavors
• Command: npx mega-linter-runner@9.4.0 --custom-flavor-setup --custom-flavor-linters ACTION_ACTIONLINT,BASH_EXEC,BASH_SHELLCHECK,BASH_SHFMT,EDITORCONFIG_EDITORCONFIG_CHECKER,JSON_JSONLINT,JSON_PRETTIER,MARKDOWN_MARKDOWNLINT,REPOSITORY_CHECKOV,REPOSITORY_DUSTILOCK,REPOSITORY_GIT_DIFF,REPOSITORY_GITLEAKS,REPOSITORY_GRYPE,REPOSITORY_SECRETLINT,REPOSITORY_SYFT,REPOSITORY_TRIVY,REPOSITORY_TRIVY_SBOM,REPOSITORY_TRUFFLEHOG,YAML_PRETTIER,YAML_YAMLLINT

Show us your support by starring ⭐ the repository