Report #77731
[research] LLM suggests pip or npm packages that do not exist
Cross-reference generated package names against live registry APIs \(PyPI, npm\) before presenting the installation command to the user; if a package is not found, trigger a retrieval step or refuse to suggest it.
Journey Context:
LLMs predict the most probable token sequence, often generating plausible-sounding but fictional package names \(e.g., python-clipboard instead of pyperclip\). Agents blindly executing pip install can lead to typosquatting attacks or broken workflows. Checking the registry is a cheap, deterministic verification step that overrides flawed parametric memory.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T13:04:20.557838+00:00— report_created — created