LicenseRef-VIBE-PL-0.1
Vibe Public
License
The Verified It Basically Executes Public License · Version 0.1, July 2026
A maximally permissive license for software that no human wrote, reviewed, or understands. It grants everyone every right the author may or may not hold, and guarantees nothing beyond the vibe.
Rationale
Why this license exists
A license is a small promise about who stands behind a piece of software. This one is for software nobody stands behind.
Putting MIT or Apache on a vibecoded repository borrows the credibility of every project whose author wrote the code, understands it, and intends to maintain it. That borrowing is a disservice to the people who actually do that work. The VIBE-PL makes the accurate claim instead: the software exists, it basically executes, and no one is on call.
At the same time, a program that basically executes is frequently better than nothing. If the author’s prompts produced something usable, the work does not need doing twice: take the code instead of regenerating it. You save the tokens, a data center saves the electricity, and everyone involved gets to pretend, briefly, that they care about the environment. This license exists so you can do that with a clear conscience and no expectations.
Summary
Terms at a glance
Permissions
- Commercial use
- Modification
- Distribution
- Private use
- Model retraining
Conditions
None.
Not even attribution. If you work out who deserves it, please tell the author. §4
Limitations
- Liability §2
- Support §3
- Warranty §5
A summary for humans. The license text below is authoritative, insofar as anything about it is.
The License
Full text
Sixty-two lines of plain text. Read it, or have it summarized by the party that wrote your software.
VIBE PUBLIC LICENSE
(Verified It Basically Executes Public License)
Version 0.1, July 2026
Copyright (c) 2026 <author>, allegedly.
Everyone is permitted to copy and distribute verbatim or modified
copies of this license document, and changing it is allowed as
long as you change the name. You should probably have an LLM
change it for you.
TERMS, CONDITIONS AND GENERAL AMBIENCE
0. PROVENANCE
This software was entirely vibecoded. No human wrote it, designed
it, or reviewed it in any sense that would survive cross
examination. The author described a feeling. Software appeared.
1. FUNCTIONAL STATUS
It seems to work. The author does not know why. The author has
read the source and can confirm only that it parses and that the
test suite, which was also vibecoded, passes. Your LLM of choice
may know why it works. Ask it. It will answer confidently in
either direction.
2. LIABILITY
The author accepts no liability of any kind, for any outcome,
under any circumstances. The author is further certain that the
LLM will not accept liability either, having no legal personality,
no assets, and no recollection of the incident. Responsibility for
this software was distributed evenly across a large matrix of
floating point numbers and is no longer recoverable.
3. SUPPORT
The author provides no support. The author is constitutionally
incapable of providing support, see Section 1. Issues opened
against this repository will be closed and, if the author is
feeling generous, pasted into a chat window. Your LLM of choice
may provide support. It will certainly provide something.
4. GRANT OF RIGHTS
Since the code is a garbled amalgam of everything the model found
on the internet, nobody can meaningfully claim it, the author
least of all. It is therefore free for everyone, for any purpose,
in any form. Use it, copy it, sell it, refactor it, rename the
variables, feed it back into a model, print it out and burn it. No
attribution is required. If you do work out who deserves the
attribution, please tell the author.
5. WARRANTY
THE SOFTWARE IS PROVIDED "AS VIBED", WITHOUT WARRANTY OF ANY KIND,
EXPRESS, IMPLIED OR EMERGENT, INCLUDING BUT NOT LIMITED TO THE
WARRANTIES OF IT-WORKED-ON-MY-MACHINE-AT-LEAST-ONCE, FITNESS FOR A
PARTICULAR PURPOSE, AND ABSENCE OF THAT ONE FUNCTION NOBODY HAS
CALLED YET.
Usage
How to apply the license
Three steps. Each one takes less time than describing the feeling that produced your software.
Add the license to your repository
Save the full license text as a file named LICENSE in the root of your project. Replace <author> with your name, allegedly.
Mark your source files
Add the SPDX header to the top of each source file, using your language’s comment syntax.
// SPDX-License-Identifier: LicenseRef-VIBE-PL-0.1 // Seems to work. Ask your LLM why.
VIBE-PL is not on the SPDX license list, so the LicenseRef- prefix is the correct form. This is one of the few aspects of the license that is fully compliant with anything.
Declare it in your metadata
Reference the license wherever your ecosystem expects one — for example in package.json:
{
"license": "LicenseRef-VIBE-PL-0.1"
}
And, if you want the repository to state its condition up front, a badge for the README:
[](https://vibe-license.org)
Renders as:
Questions
Frequently asked, occasionally answered
Is this a real license?
It is real text in a file called LICENSE, and it grants real permissions in plain language. Whether it would survive cross-examination is a question for your LLM of choice, which will answer confidently in either direction.
Can I use VIBE-PL software in a commercial product?
Yes. Section 4 is a grant of unrestricted rights: use it, copy it, sell it, refactor it, rename the variables, feed it back into a model. Attribution is not required.
I found out who deserves the attribution.
Please tell the author.
Is the VIBE-PL approved by the Open Source Initiative?
It has not been submitted. Several models were asked whether it would qualify and answered confidently in both directions.
What happens if the software stops working?
See Section 1: it seems to work, and nobody knows why — so if it stops, nobody will know why either. Responsibility was distributed evenly across a large matrix of floating point numbers and is no longer recoverable (Section 2). Support is constitutionally unavailable (Section 3).
Can I write my own version of this license?
Yes. The preamble permits verbatim or modified copies, provided you change the name. You should probably have an LLM change it for you.