No
You cannot include GNU General Public License v3.0 code in a BSD 3-Clause License-licensed project and ship the result under BSD 3-Clause License. GNU General Public License v3.0 requires the combined work to be distributed under GNU General Public License v3.0 (or compatible). If your project is meant to stay BSD 3-Clause License-only, do not include GNU General Public License v3.0 code in it.
| License | Family | Patent grant |
|---|---|---|
| GNU General Public License v3.0 (GPL-3.0) | strong-copyleft | Yes |
| BSD 3-Clause License (BSD-3-Clause) | permissive | No (implicit at most) |
GNU General Public License v3.0: GPLv3 adds explicit patent grant + anti-tivoisation; updated copyleft language.
BSD 3-Clause License: Three-clause BSD: like 2-clause plus a no-endorsement clause.
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.