No
You cannot include GNU GPL v3.0 or later code in a zlib License-licensed project and ship the result under zlib License. GNU GPL v3.0 or later requires the combined work to be distributed under GNU GPL v3.0 or later (or compatible). If your project is meant to stay zlib License-only, do not include GNU GPL v3.0 or later code in it.
| License | Family | Patent grant |
|---|---|---|
| GNU GPL v3.0 or later (GPL-3.0-or-later) | strong-copyleft | Yes |
| zlib License (Zlib) | permissive | No (implicit at most) |
GNU GPL v3.0 or later: GPL-3.0 with explicit upgrade path; users may pick GPL-3.0 or any later GPL.
zlib License: Permissive, with a misrepresentation-of-origin 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.