This is extremely broad and should be policed by the vendor the not @github.

Do not merge.

The term "jailbreaking" is usually associated with Apple products only and is extremely important for both keeping Apple products secure and the end-users. Most vulnerabilities in Apple are found using jailbroken products.

One such perfect example is the OpenCore bootloader: https://dortania.github.io/OpenCore-Install-Guide/

As a strict good-faith security researcher, who runs a powerful serial number generator for macOS related products that enables researchers to discover flaws in iMessage & Facetime, two critical communication protocols, https://github.com/sickcodes/osx-serial-generator, I have done extensive work in providing access to macOS virtual systems for independent security researchers, and those who can't afford a real mac, but still want to participate in Apple Bug Bounty ($X00,000 bounties).

Apple has very strict requirements: https://developer.apple.com/security-bounty/requirements/ that state,

You are entirely permitted to violate the EULA of Apple products, if you find and report bugs directly to Apple.

In fact, Apple ENCOURAGES you to break the EULA to report bugs to them.

8. A participant in the Apple Security Bounty program (“ASB Participant”) will not be deemed to be in breach of applicable Apple license provisions which provide that a user of Apple software may not copy, decompile, reverse engineer, disassemble, attempt to derive the source code of, decrypt, modify, or create derivative works of such Apple software, for in scope actions performed by that ASB Participant where all of the following are met:

The actions were performed during good-faith security research, which was — or was intended to be — responsibly reported to Apple;
The actions were performed strictly during participation in the Apple Security Bounty program; and
Neither the actions nor the ASB Participants have otherwise violated these policies such as violating legal requirements 1, 2, and 3, above.

Therefore, @github should not be the one to police another company's EULA. A company's EULA is not the law. Moreover, this has nothing to do with DMCA.

In Apple's case, you are given explicit permission that supersedes all other EULAs, so as long as you report the bugs to Apple security team.

Another such cases are WordPress plugins which must be released under the GPLv3+ License, and hence, any such serial number generator is absolutely permitted under the license.

If GitHub feels like becoming the serial number police and hiring a bunch of lawyers to go through each EULA instead of letting the vendor make their own calls, this would limit productivity in security research and ultimately roll-back any current progress that has been made in bridging Developers with Security.

@github should not get involved in policing serial numbers and this should not be merged.

https://sick.codes/is-hackintosh-osx-kvm-or-docker-osx-legal/