i-have-adhd License: MIT Licensing Explained for the ADHD-Friendly Project

The i-have-adhd project is released under the MIT License, a permissive open-source license that allows unrestricted commercial and personal use provided the copyright notice and license text are preserved.

The i-have-adhd repository (ayghri/i-have-adhd) provides ADHD-friendly interaction patterns and tooling for developers. Understanding the i-have-adhd license terms is essential for anyone integrating this code into applications, extending its functionality, or distributing derivative works. The project explicitly adopts the MIT License to maximize compatibility while maintaining minimal legal overhead for contributors and users.

What License Does i-have-adhd Use?

The repository distributes all source code under the MIT License. You can find the complete legal text in the LICENSE file located at the repository root (https://github.com/ayghri/i-have-adhd/blob/main/LICENSE). This permissive licensing choice reflects the project's goal of widespread adoption: developers may freely incorporate the ADHD-friendly response rules and runtime behaviors into both open-source and proprietary software stacks without the copyleft obligations associated with GPL-style licenses.

MIT License Permissions and Requirements

The MIT License governing i-have-adhd grants broad freedoms while imposing specific attribution requirements.

Permissions Granted

The license explicitly permits anyone to:

• Use the software for personal, educational, or commercial purposes
• Copy and modify the source code to fit specific needs
• Merge the code into larger projects
• Publish, distribute, and sublicense copies
• Sell the software or derivative works without royalty obligations

These permissions apply globally and do not discriminate against fields of endeavor.

Conditions You Must Follow

To legally redistribute i-have-adhd code or include it in your own projects, you must:

• Include the copyright notice: Preserve the original attribution to "Ayoub Ghriss" and the year 2026 as specified in the LICENSE file
• Distribute the license text: Include a copy of the MIT License text in all copies or substantial portions of the software

Failure to include these notices technically violates the license terms, though the MIT License remains one of the most legally straightforward open-source licenses to comply with.

Liability Limitations

The software is provided "as is", without warranty of any kind. The authors are not liable for any damages arising from the use or inability to use the software, including but not limited to data loss or business interruption.

How to Comply with the i-have-adhd License

Proper compliance ensures you maintain legal protection while benefiting from the project's ADHD-friendly tooling.

Adding License Headers to Source Files

When incorporating i-have-adhd code into your own files, add a header comment referencing the original copyright and license:

/**
 * i-have-adhd
 * Copyright (c) 2026 Ayoub Ghriss
 *
 * Licensed under the MIT License.
 * See the LICENSE file in the repository root for full details.
 */

This header explicitly acknowledges the upstream LICENSE terms while documenting the code's origin for future maintainers.

Declaring the License in package.json

If you publish the project as an npm package or fork the repository, update your package.json metadata to reflect the MIT status:

{
  "name": "i-have-adhd",
  "version": "1.0.0",
  "license": "MIT",
  "repository": {
    "type": "git",
    "url": "git+https://github.com/ayghri/i-have-adhd.git"
  }
}

The "license": "MIT" field enables automated license scanners to correctly identify your project's compliance status.

Verifying the License Programmatically

For build pipelines or compliance automation, you can read and display the license text at runtime:

const fs = require('fs');
const license = fs.readFileSync('LICENSE', 'utf8');
console.log('Project License:\n', license);

This Node.js snippet outputs the full MIT License text, useful for generating attribution pages or legal documentation in applications that bundle i-have-adhd components.

Key Files Related to Licensing

Several files in the repository define the legal and behavioral boundaries of the project:

• LICENSE — Contains the complete MIT License text governing all source code in the repository
• package.json — Declares the "license": "MIT" metadata field for package managers and automated tools
• README.md — Provides project overview and usage instructions, often referencing licensing terms
• AGENTS.md — Documents runtime entry points and agent interaction guidelines, subject to the same MIT terms
• skills/i-have-adhd/SKILL.md — Defines the canonical ADHD-friendly response rules, licensed under MIT

Summary

• The i-have-adhd project uses the MIT License, a permissive open-source license compatible with both commercial and proprietary projects
• Attribution is mandatory: You must include the original copyright notice (Ayoub Ghriss, 2026) and full license text in any redistribution
• The license permits unrestricted use, including modification, sublicensing, and sale, without requiring source code disclosure
• Key compliance files include the root LICENSE, package.json, and source file headers
• No warranty is provided; use the code at your own risk

Frequently Asked Questions

Is the i-have-adhd project free for commercial use?

Yes. The MIT License explicitly permits commercial use without requiring payment or royalty obligations. You may incorporate the code into proprietary products, SaaS applications, or commercial distributions, provided you maintain the copyright notice and license text as specified in the repository's LICENSE file.

What happens if I don't include the MIT License notice in my project?

Technically, redistributing the code without the required copyright notice and license text constitutes a violation of the MIT License terms. While the MIT License is not "viral" (it does not infect your entire codebase), failure to include attribution could expose you to copyright infringement claims. Best practice is to copy the LICENSE file from the original ayghri/i-have-adhd repository into your distribution.

Can I change the license of code derived from i-have-adhd?

Yes. The MIT License allows you to sublicense the work, meaning you can incorporate i-have-adhd code into a larger project distributed under a different license (including proprietary licenses). However, the original i-have-adhd source files must retain their MIT License notices. You cannot remove the MIT License from the specific files you copied, but you can apply different terms to your own additions and modifications.

Who holds the copyright for the i-have-adhd project?

The copyright is held by Ayoub Ghriss (copyright year 2026), as stated in the LICENSE file at the repository root. Any contributions to the project are presumed to be licensed under the same MIT terms unless explicitly stated otherwise, following standard open-source contribution conventions.

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