Head to head
Devin vs GitHub Copilot
Comparing 9 documented Devin incidents against 6 for GitHub Copilot.
What these records show
Devin has the lower average severity among the incidents collected here (2.4 vs 7.3 for Devin and GitHub Copilot, from 9 and 6 incidents). These records can't establish which agent is safer: counts reflect how widely each is used and how often people report failures, not a failure rate.
| Metric | Devin | GitHub Copilot |
|---|---|---|
| Documented incidents | 9 | 6 |
| Average severity | 2.4 | 7.3 |
| Critical | 0 | 0 |
| High | 0 | 5 |
| Source checked | 9 | 6 |
Severity at a glance
Devin
2.4
low
GitHub Copilot
7.3
high
Failure modes
DevinDistribution of failure modes across all documented incidents.
GitHub CopilotDistribution of failure modes across all documented incidents.
The incidents behind these numbers
Devin
5.0Devin replaced entire medical website with unrelated renal care site3.0Devin CI workflow caused 836-comment spam storm on single PR2.0Devin built 13,600-line app with build failure instead of lean campaign dashboard2.0Devin PR broke ledger list API and created buckets on deleted resources2.0Devin repeatedly submitted identical docs PRs that kept getting rejected
GitHub Copilot
8.0GitHub Copilot CLI ran arbitrary attacker commands via a nested bare git repository abusing core.fsmonitor (CVE-2026-45033)8.0GitHub Copilot suggested 2,702 valid secrets — 33% of extracted keys were real, live credentials8.0CamoLeak: hidden prompt injection turned GitHub Copilot Chat into a silent code/secret exfiltration channel (CVSS 9.6)8.0Rule Files Backdoor: hidden Unicode in config files made Copilot and Cursor emit malicious code7.0Copilot CLI's checkpoint restore ran git clean -fd and destroyed 1GB of evaluation data the agent never touched