No
You cannot include GNU GPL v2.0 or later code in a BSD 2-Clause License-licensed project and ship the result under BSD 2-Clause License. GNU GPL v2.0 or later requires the combined work to be distributed under GNU GPL v2.0 or later (or compatible). If your project is meant to stay BSD 2-Clause License-only, do not include GNU GPL v2.0 or later code in it.
| License | Family | Patent grant |
|---|---|---|
| GNU GPL v2.0 or later (GPL-2.0-or-later) | strong-copyleft | No (implicit at most) |
| BSD 2-Clause License (BSD-2-Clause) | permissive | No (implicit at most) |
GNU GPL v2.0 or later: GPL-2.0 with explicit upgrade path; users may pick GPL-2.0 or any later GPL.
BSD 2-Clause License: Two-clause BSD: very similar to MIT, no patent grant.
If you found this page because you're trying to figure out whether shipping a particular dependency is safe, the answer above is a starting point — not a substitute for reading the actual licenses or talking to a lawyer when stakes are high.
LicenseHound walks every transitive dependency in your repo, maps each to its SPDX license, and flags pairs like this one in PR comments. The CLI is free; the team dashboard is paid.