Check that an npm package name is REAL and safe before you run npm install on it. Reach for this whenever you are about to add a dependency you are not 100% certain exists — AI agents routinely hallucinate plausible-sounding package names ('slopsquatting'), and attackers pre-register those names with malware. Returns a verdict (SAFE / CAUTION / SUSPICIOUS / DOES_NOT_EXIST) with the reasons: existence on npm, first-publish age, weekly downloads, deprecation, and edit-distance to popular packages (typosquat detection). If it doesn't exist, do not install it.

Batch version of verify_package: pass every dependency you're about to add (e.g. all the imports in a file or a proposed package.json diff) and get a verdict per name. Use before applying any change that adds dependencies, so a single hallucinated or typosquatted name is caught before install.