← docs

Troubleshooting

Common issues when installing or running the Scanner, and how to resolve them.


No comment appears on my PR

Likely cause: the App isn’t installed on this repo.

Visit the GitHub App settings → Configure → check the repo list. If it’s missing, add it.

Likely cause: the PR has no Python file changes.

The Scanner only runs when the PR diff includes .py files. PRs that only modify YAML, Markdown, or other non-Python files are skipped.

Likely cause: AST parse error on a file in your diff.

If a file fails to parse (syntax error mid-PR), the Scanner skips it and notes it in the comment. Fix the syntax error and push again.

Comment says “license invalid”

Confirm your license key is correctly stored. For the GitHub App, license is automatic — contact support. For the GitHub Action, check that the AI_FOOTPRINT_LICENSE secret is set in repo or org-level secrets.

Findings include false positives

The Scanner uses AST analysis, so it shouldn’t match library names in strings, comments, or docstrings. If you’re seeing one anyway, file an issue with the failing file. Most false positives have been from non-standard import styles — the AST visitor handles most of them, but edge cases exist.

Findings are missing imports I’d expect

Two common causes:

  1. The library isn’t in any tier of risk_definitions.yml. See Configure risk_definitions.yml.
  2. The import is dynamic (importlib.import_module("openai")). The Scanner does not detect dynamic imports; this is a known limitation.

Still stuck

Email zheneewong@gmail.com with your repo name, the PR number, and a description of what you expected vs what you saw.