By Vero SecurityBuilt and funded by Vero Security, the AI Security Engineering platform.Read the charter

Dependency risk and package hallucination

Every dependency an agent adds is code you now trust, and models sometimes invent package names that attackers then register, a tactic known as slopsquatting. Health signals like OpenSSF Scorecard and explicit rules for AI assistants help keep agent-chosen dependencies in check.

Read in this order

  1. PaperWe Have a Package for You! A Comprehensive Analysis of Package Hallucinations by Code Generating LLMsStart here: measured data on how often code models invent package names.
  2. OfficialSecurity-Focused Guide for AI Code Assistant Instructions (OpenSSF)Instruction rules you can give a coding assistant to pick safer dependencies.
  3. OfficialOpenSSF ScorecardAn automated health check you can run on any open source package.

Save your progress

We email you a sign-in link. No password.

By signing in you agree to the terms. The privacy policy explains how we use your details.

Join the AI security engineering community

Free. Roadmap updates, chapters near you, and first word when credentials open.

We’ll email you community updates. Unsubscribe anytime. By sending this you agree to the terms. The privacy policy explains how we use your details.