Add edge-case tests for empty and non-Python scan targets

[Johnkothapalli]

Problem

The analyzer has limited coverage for valid targets that contain no Python files or point to a non-Python file. The intended CLI output and exit behavior should be explicit and stable.

Proposed scope

Add tests that document behavior for an empty directory, a directory containing only non-Python files, and a direct non-Python file target. If current behavior is inconsistent, propose the smallest compatible correction.

Acceptance criteria

• tests use temporary directories and files;
• no platform-specific paths;
• expected file count, score, text output, and exit code are asserted;
• README is updated only if user-visible behavior changes;
• no new dependency is introduced.

This is suitable for a first contribution. Comment to claim it before opening a pull request.

[PuneetRana7]

Hi, I'd like to work on this issue. I'll add tests for the empty directory, directory containing only non-Python files, and direct non-Python file target, following the acceptance criteria.

[Johnkothapalli]

Thanks, @PuneetRana7 — the issue is assigned to you. Your proposed scope matches the acceptance criteria.

Please assert the observable results for all three targets (file count, score/text output, and CLI exit code) using temporary paths. Start with tests; if they expose inconsistent behavior, keep any production change to the smallest compatible fix and explain it in the PR. No README or changelog change is needed unless behavior changes.

Before submitting, please run at least the focused tests plus ruff check . and mypy; the full CI matrix will run on the PR. There is no deadline—comment here if anything is unclear or you need the issue released.