fix: run scanner from /app directory to prevent module resolution conflict

[williambrady]

Summary

• Fixes a bug where the scanner's entrypoint executes the scanned repo's src/main.py instead of its own when the target repo contains a src/main.py module
• Adds cd /app before python -m src.main in entrypoint.sh so Python module resolution starts from the scanner's install directory

Root Cause

The GitHub Action runs with /github/workspace as the working directory. python -m src.main resolves modules relative to the current directory first, so if the scanned repository has its own src/main.py, Python executes that instead of the scanner's code at /app/src/main.py.

Test plan

• Run the scanner against a repo that has its own src/main.py and verify the scanner executes correctly
• Run the scanner against a repo without src/main.py to confirm no regression

[ghaworkflow]

Looks like it should work.

[augmentcode]

🤖 Augment PR Summary

Summary: Adjusts the action entrypoint to run the scanner from its installed /app directory so Python resolves src.main from the scanner, not the scanned repository.

Change: Updates entrypoint.sh to cd /app before invoking python -m src.main, preventing module-name collisions when a target repo contains src/main.py.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. No suggestions at this time.

Comment augment review to trigger a new review at any time.

[Copilot]

Pull request overview

This PR fixes a critical bug where the scanner could execute a scanned repository's src/main.py instead of its own when Python module resolution prioritizes the current working directory. The fix changes the working directory to /app (the scanner's installation directory) before executing the scanner's main module.

Changes:

• Modified entrypoint.sh to cd to /app before running the Python scanner module, preventing module resolution conflicts

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.