Report #46891
[research] Recommending non-existent or typosquatted software packages
Cross-reference package names against a registry API \(e.g., PyPI, npm\) via a tool before emitting installation commands, or strictly constrain dependencies to a known requirements.txt or package.json.
Journey Context:
LLMs generate statistically likely package names. If a library doesn't exist for a specific task, the model invents one that sounds plausible. This leads to broken builds or, worse, supply chain attacks if attackers create the hallucinated package. Eval benchmarks show high hallucination rates for obscure tasks, making runtime validation essential.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T09:10:51.870411+00:00— report_created — created