Holehe License Details: GNU General Public License v3.0 Explained

The Holehe project is released under the GNU General Public License version 3.0 (GPL‑3.0), a strong copyleft license that requires all distributed derivatives to use the same license.

Holehe, the open-source email tool developed by Megadose, is freely available for modification and redistribution under strict copyleft terms. Understanding these Holehe license details is essential for anyone planning to use, modify, or incorporate this osint tool into their own projects.

What License Governs Holehe?

The repository megadose/holehe uses GPL‑3.0 as its sole license. This is confirmed in two locations:

• The README.md file contains an explicit license reference linking to GPL‑3.0
• The complete license text resides in LICENSE.md at the repository root

According to the Holehe source code, no alternative licensing options are offered. All contributions to the project fall under this single license framework.

Core Permissions Under GPL‑3.0

The Holehe license details grant four fundamental freedoms to users:

Freedom	Description
Run	Use Holehe for any purpose without restriction
Study	Access and examine the complete source code
Share	Redistribute copies of the original software
Modify	Create and distribute derivative works

These permissions come with binding obligations that preserve the open-source nature of the codebase.

Key Obligations for Users and Developers

Source Code Availability

Any distribution of Holehe—whether original or modified—must include the complete corresponding source code or a written offer to provide it. This requirement is enforced through the copyleft mechanism in LICENSE.md.

License Preservation

When you redistribute Holehe or create derivatives, you must:

• Retain the original copyright notices
• Apply GPL‑3.0 to your distributed versions
• Include a copy of the full license text
• Document any changes made to the source files

No Additional Restrictions

The Holehe license details explicitly prohibit imposing further limitations. You cannot add clauses that restrict the GPL‑3.0 rights from being passed to subsequent recipients.

Practical Implications for Different Use Cases

Personal or Internal Use

If you use Holehe privately without distribution, no obligations apply. You may modify the code in holehe/core.py or any module without disclosure requirements.

Public Distribution or SaaS Deployment

Once you distribute Holehe binaries or offer it as a service, the copyleft trigger activates. Your modifications to files like holehe/modules/programming/github.py or custom module additions must be released under GPL‑3.0.

Incorporating Holehe into Larger Projects

GPL‑3.0 is incompatible with proprietary software. You cannot link Holehe code against closed-source applications. Any combined work must be licensed entirely under GPL‑3.0.

Where to Find Official License Information

The Holehe repository provides authoritative sources:

1. README.md — Contains the license declaration and a direct link to the full text
2. LICENSE.md — Houses the verbatim GPL‑3.0 legal text as published by the Free Software Foundation

Always reference these files in the megadose/holehe repository for the current binding version.

Summary

• Holehe uses GPL‑3.0 exclusively with no dual-licensing options
• The license is documented in LICENSE.md and referenced in README.md
• Users gain full freedoms to run, study, share, and modify
• Distribution triggers copyleft obligations requiring source disclosure
• No additional restrictions can be imposed on recipients

Frequently Asked Questions

Can I use Holehe in a commercial product?

Yes, but with conditions. You may sell Holehe or include it in commercial offerings, provided you comply with GPL‑3.0 terms. This means releasing your complete source code under the same license and not adding proprietary restrictions. Commercial use is permitted; proprietary bundling is not.

Do I need to share my modifications if I only use Holehe internally?

No. The distribution requirement only activates when you convey the software to others. Private modifications to holehe/modules/ or core files can remain undisclosed if the software never leaves your organization.

Is Holehe compatible with MIT or Apache-2.0 licensed code?

Code combining is possible but complex. GPL‑3.0's copyleft provisions take precedence in any integrated work. MIT-licensed components can be incorporated into Holehe, but Holehe cannot be incorporated into MIT-licensed projects without converting the entire work to GPL‑3.0. Apache-2.0 presents additional patent clause considerations that require legal review.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}