Extra results printed, when running bandit on file that doesnt exist

When running bandit on a file that doesn't exist, it still gives the results as if it found the file and ran the project, saying 0 issues found. Then when you go the bottom of the results it then says one file skipped and says (example.py (No such file or directory)).

There should be an added functionality that is added where it just says no such file found, instead of acting like it "ran the file"

example below:

(Desktop) Omars-MacBook-Air:bandit omar$ bandit example.py
[main]  INFO    profile include tests: None
[main]  INFO    profile exclude tests: None
[main]  INFO    cli include tests: None
[main]  INFO    cli exclude tests: None
[main]  INFO    running on Python 3.7.4
Run started:2023-03-28 01:16:36.366190
Test results:
        No issues identified.
Code scanned:
        Total lines of code: 0
        Total lines skipped (#nosec): 0
Run metrics:
        Total issues (by severity):
                Undefined: 0
                Low: 0
                Medium: 0
                High: 0
        Total issues (by confidence):
                Undefined: 0
                Low: 0
                Medium: 0
                High: 0
Files skipped (1):
        example.py (No such file or directory)
(Desktop) Omars-MacBook-Air:bandit omar$

Start by reproducing the issue with bandit example.py, then trace the CLI handling for nonexistent input files and the reporting of skipped files. Done means a missing file reports that it was not found without presenting a normal successful scan with zero issues; verify the existing command output after the change.