No
You cannot include GNU General Public License v2.0 code in a Creative Commons Zero v1.0 Universal-licensed project and ship the result under Creative Commons Zero v1.0 Universal. GNU General Public License v2.0 requires the combined work to be distributed under GNU General Public License v2.0 (or compatible). If your project is meant to stay Creative Commons Zero v1.0 Universal-only, do not include GNU General Public License v2.0 code in it.
| License | Family | Patent grant |
|---|---|---|
| GNU General Public License v2.0 (GPL-2.0) | strong-copyleft | No (implicit at most) |
| Creative Commons Zero v1.0 Universal (CC0-1.0) | permissive | No (implicit at most) |
GNU General Public License v2.0: Strong copyleft: derivative works distributed must also be GPL-2.0.
Creative Commons Zero v1.0 Universal: Public-domain dedication; primarily for content but seen on some code.
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.