Use scan command in favor of check one for safety

[jorgepiloto]

Currently, [safety] uses the [check] command, see:

actions/check-vulnerabilities/action.yml

Line 315 in 126c7eb

safety check -o bare --save-json info_safety.json --continue-on-error $ignored_vulnerabilities

However, I started to get this notification:

DEPRECATED: this command (`check`) has been DEPRECATED, and will be unsupported beyond 01 June 2024.

We highly encourage switching to the new `scan` command which is easier to use, more powerful, and can be set up to mimic the deprecated command if required.

We should migrate to the new command.

[RobPasMue]

Correct - I started working on this (back in July 2024) but their claim of "being easier to use, more powerful and can be set up to mimic..." is not true The output JSON file had a different structure and required adapting all our scripts. I will continue this work - thanks @jorgepiloto

[RobPasMue]

Also - the affected package is not bandit but safety

[PProfizi]

Hi all,
Just to get some clarification, is this the reason I get a failing vulnerability check here?
Or is this not supposed to make the job fail?

[RobPasMue]

Nope - this shouldn't mark the job as failed @PProfizi.