What are the security implications of enabling Dependabot auto-merge without proper review gates?

Auto-merge without adequate safeguards can introduce a genuine supply-chain risk: if a compromised or maliciously altered package version passes CI (which tests your code's behavior, not the dependency's internal trustworthiness) and matches your auto-merge criteria, it merges into your codebase with no human review at all — exactly the kind of software supply-chain attack pattern that has caused real, high-profile incidents in the broader ecosystem.

flowchart LR
    A[Malicious package version published] --> B{Passes CI checks?}
    B -->|Yes, and matches auto-merge rule| C[Auto-merged with zero human review]
    C --> D[Compromised code now in production]

Mitigations include restricting auto-merge strictly to low-risk categories (patch-only, well-established dependencies with a long track record), requiring at minimum a passing security scan (not just functional tests) as a merge gate, and considering exclusions for dependencies with unusually low download counts or very recent publication (both signals sometimes associated with supply-chain attacks), rather than applying auto-merge as a blanket policy across every dependency regardless of these risk signals.