VibeCoded AI-Slop License v1.0 Sets Legal Disclaimers for Prompted Repositories
Developer Nicolas CARPi published the VibeCoded AI-Slop License v1.0 to explicitly disclaim maintenance, quality, and liability for AI-generated code. It gives vibe coders a ready-to-use template for disposable prototypes containing hallucinated abstractions.
Impact: Low
Why it matters
You can add this license to your rapid AI experiments to explicitly warn users against production deployments and disclaim maintenance obligations.
TL;DR
- 01Provides a dedicated disclaimer license tailored for quick vibe-coded projects and AI prototypes.
- 02Explicitly states that code is provided 'AS VIBECODED' with zero expectation of human verification or maintenance.
- 03Permits any downstream usage, commercial exploitation, model training, and modifications without restrictions.
Key facts
- License Name
- VibeCoded AI-Slop License v1.0
- Warranty Terms
- AS IS, AS GENERATED, AS VIBECODED
Purpose of the AI-Slop License
The VibeCoded AI-Slop License v1.0 was created to match the modern reality of agentic development where codebases are generated in response to vague prompts without exhaustive human review. It explicitly acknowledges that dependencies might not exist, abstractions may be unnecessary, and the original author might not know how the system operates.
Key Terms and Disclaimers
Under the license terms, recipients are permitted to:
- Use, copy, modify, distribute, sublicense, sell, or delete the software without publishing changes.
- Retrain AI models on the codebase or use AI to rewrite it.
- Submit pull requests or open issues without any guarantee that they will ever be reviewed.
Additionally, the warranty disclaimer covers liability for production incidents, data loss, mysterious cloud bills, and broken dependencies.
Try it in 2 minutes
THE SOFTWARE IS PROVIDED "AS IS", "AS GENERATED", "AS VIBECODED", AND WITH ALL FAULTS.
THE AUTHORS DISCLAIM ALL WARRANTIES INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND MAINTAINABILITY.markdown
✓ When to use
- Use in open-source throwaway experiments and weekend prototypes built primarily with LLM generation.
- Use when you want to explicitly signal zero long-term maintenance commitment on public GitHub gists.
✕ When NOT to use
- Do not use in commercial client deliverables requiring strict legal compliance and copyright provenance.
- Not suitable for mission-critical software where formal enterprise support or SLA commitments are expected.
What to do today
- Add the VibeCoded license text as LICENSE in experimental AI repositories to set clear expectations.
- Audit vibe-coded dependency trees before deploying any open-source AI prototype to real infrastructure.
Sources