GPL3 license and "vibecoded" code. Accepted provided it's all directed by user? Or goes against GPL3, and is limited to MIT only?

[DuckersMcQuack]

Discussion Type

Question

Discussion Content

I need to make 100% sure regarding the licenses, as i'm very slow on understanding things if written a certain way most of the time. So i need to ask:

If a code under GPL3 has been altered with vibecoding, aka you direct the llm (either locally, or git copilot/claude/gpt etc), Can it too fall under GPL3 provided it follows the same structure of providing it's GPL3 license? Or would vibecoded code only be allowed on git if it's MIT and not using anything that isn't MIT if shared?

As i want to make 100% sure i do things correctly and follow all guidelines properly.

I've asked on reddit, asked claude, and now one last time on github forums to take in as many angles as i can. As GPL3 didn't mention llm/vibecoded/copilot, or anything related, thus i have to ask and make 100% sure.

[razakhan83]

f you modify GPLv3 code using an AI (vibecoding), the new version must remain GPLv3. Because the original license is copyleft, any derivative work regardless of whether it was written by you or an LLM is legally bound to the same terms. You cannot switch it to MIT if the foundation is GPLv3; you must keep the original license, include a notice of your changes, and ensure the source code stays open to everyone.

[DuckersMcQuack]

f you modify GPLv3 code using an AI (vibecoding), the new version must remain GPLv3. Because the original license is copyleft, any derivative work regardless of whether it was written by you or an LLM is legally bound to the same terms. You cannot switch it to MIT if the foundation is GPLv3; you must keep the original license, include a notice of your changes, and ensure the source code stays open to everyone.

Absolutely. No plans to switch from and to any license if one is MIT, and another is GPL3 for instance, i'd then pick an MIT alternative of the MIT code, and vice versa if there was no GPL3 available to achieve X.

And all the code will stay fully open. Even include .sh to build for linux, .bat for windows if i make it go both directions that will auto create venv with dependenciesto to compiled the program.

Just needed to make sure that "vibecoded" code is still fine under GPL3.

And had claude suggest this.

Would you say this is perfectly structured to include all that's needed for the licenses and so on?

my-project/
├── LICENSE                          # Your project's GPL3 license
├── NOTICE                           # Summary of all third-party components used
├── CHANGELOG.md                     # Your project's own changelog
│
├── src/                             # Your original source code
│   └── ...
│
├── third-party/                     # All upstream GPL3 code lives here
│   │
│   ├── nvidia-patch/                # Example: keylase/nvidia-patch
│   │   ├── UPSTREAM_README.md       # Original README preserved
│   │   ├── UPSTREAM_LICENSE         # Original GPL3 license from that repo
│   │   ├── SOURCE_INFO              # Upstream URL, commit hash, date fetched
│   │   ├── CHANGES.md               # YOUR changes to this code, explicitly listed
│   │   └── src/                     # The (modified) upstream source files
│   │       └── ...
│   │
│   └── some-other-gpl3-project/
│       ├── UPSTREAM_README.md
│       ├── UPSTREAM_LICENSE
│       ├── SOURCE_INFO
│       ├── CHANGES.md
│       └── src/
│           └── ...
│
└── licenses/                        # Central license directory
    ├── GPL-3.0.txt                  # Full GPL3 license text
    ├── README.md                    # Explains what each component is and its license
    ├── nvidia-patch_LICENSE         # Copy of nvidia-patch's license
    └── some-other-project_LICENSE   # Copy of the other project's license

[mecodeatlas]

Thanks for posting in the GitHub Community, @DuckersMcQuack!

We're happy you're here. You are more likely to get a useful response if you are posting your question in the applicable category, the Discussions category is solely related to conversations around the GitHub product Discussions. This question should be in the Programming Help category. I've gone ahead and moved it for you. Good luck!

[frazrajpoot01]

Hi there! 👋 I saw your discussion and wanted to jump in to give you a definitive answer so you can be 100% sure about your licensing moving forward.

To give you the short and direct answer: Yes, this structure is absolutely perfect. It is exceptionally well-organized and goes above and beyond what most open-source projects do. By using this exact structure, you are flawlessly fulfilling all the legal obligations of the GPLv3 license, regardless of whether the code in your src/ folder was hand-typed or "vibecoded" using an LLM.

Here is exactly why the structure you shared is a gold standard for your situation:

1. You are fulfilling GPLv3 Section 5(a)

The GPLv3 license strictly requires that if you modify someone else's GPL code, you must carry "prominent notices stating that you modified it." Your inclusion of the CHANGES.md file inside each third-party/ subdirectory handles this perfectly.

2. You are preserving Upstream Licenses

GPLv3 requires you to keep existing copyright and license notices intact. By keeping the UPSTREAM_LICENSE and UPSTREAM_README.md right next to the modified source code, nobody can ever accuse you of stripping away the original authors' credit.

3. Clear Separation of Concerns

By keeping your original "vibecoded" project strictly in src/ and the upstream dependencies in third-party/, it is 100% clear to anyone auditing your project which parts are your new GPLv3 contributions and which parts are inherited from others.

---

Two Quick "Pro-Tips" to Make it Bulletproof

Since you want to be as legally safe and correct as possible, here are two tiny additions to keep in mind:

• File Headers: While your folder structure is perfect, the Free Software Foundation (the creators of GPL) highly recommends putting a short comment at the very top of your individual source code files (inside your src/ folder) stating the copyright year, your name (or handle), and that the file is licensed under GPLv3.
• The NOTICE file: Using a NOTICE file is technically a requirement of the Apache 2.0 license, not GPLv3. However, keeping it as a general "credits and attributions" file is a fantastic practice and perfectly fine to include. Just list all the third-party tools and their original authors there.

Final Verdict: You are fully cleared to proceed. Drop your vibecoded files into src/, keep your dependencies neatly tracked in third-party/, and release your project to the world! You have structured this incredibly well. 🚀

[hardik121121]

The existing answers confirm the GPL3 mechanics correctly, but there's one underlying concern your question touches on that's worth addressing directly: who actually owns AI-generated code, and does that affect GPL3 compliance?

The short answer: when you're directing an LLM as a tool, you're the author of the output. The major AI coding tools (Copilot, Claude, ChatGPT) all explicitly state in their Terms of Service that the generated output belongs to you, not them. So from a copyright standpoint, vibecoded code directed by you = your code.

This matters for GPL3 because copyleft only functions when there's a valid copyright holder. If you own the output, GPL3 applies to it exactly as it would to hand-typed code.

Practical summary for your situation:

• Modifying existing GPL3 code with an LLM → derivative work → must stay GPL3 ✓
• Writing new code with an LLM as a tool for a GPL3 project → your code → GPL3 applies normally ✓
• The method of writing (keyboard vs. AI prompt) has no legal relevance to the license

The one caveat worth knowing: The US Copyright Office has said purely AI-generated content with no human creative input may not be copyrightable at all. But "vibecoding" where you're prompting, reviewing, iterating, and directing the output has human creative input throughout — so this edge case almost certainly doesn't apply to your workflow.

Your folder structure is solid. You're good to proceed.