Hit a false positive? Post it here.

[heavykenny]

v0.9.3 cut findings by 38% across 70 OSS repos, entirely on community-flagged false positives. We didn't disable a single rule. We tightened them so they survive real code.

If you hit one:

1. Copy the code aislop flagged (3-5 lines of context is plenty)
2. Name the rule (e.g. ai-slop/narrative-comment)
3. Tell us why you think it's a false positive

We'll either fix the rule or explain why we think it's a real catch (and we'll listen if you push back).

Don't suppress the rule first. False positives are a bug in the rule, not in your code.

— Kenny

[cbuctok]

False positive: ai-slop/hallucinated-import on psycopg2

Flagged code (from scripts/export_db.py, line 67, with context)

pyproject.toml:

[project]
dependencies = [
    "psycopg2-binary ≥2.9",
]

scripts/export_db.py:

import psycopg2   # line 67

Rule name

ai-slop/hallucinated-import

Why this is a false positive

The package psycopg2-binary provides the psycopg2 import - it's the official pre‑built wheel on PyPI. The source‑distribution psycopg2 also exists but is effectively deprecated; both expose the same top‑level module. This follows standard PyPI naming conventions (e.g. Pillow → PIL, pyyaml → yaml).

The root cause is that the PYTHON_IMPORT_TO_PIP mapping in src/engines/ai-slop/python-data.ts is missing:

"psycopg2": "psycopg2-binary",

Suggested fix: add that mapping. The existing checkPyImport already handles submodules (psycopg2.extras, etc.) correctly because it only checks the root package name.

[heavykenny]

Thank you @cbuctok for creating this, I will fix and let you know.

[heavykenny]

@cbuctok trust you are well. we made a new release and should resole this fp. can you check again with npx aislop@latest scan and let me know.

[cbuctok]

@heavykenny
I confirm it was fixed in v0.10.1 - import psycopg2 from psycopg2-binary no longer triggers hallucinated- import.
Thank you very much for the quick turnaround!
Cheers