i-have-adhd MIT License and Attribution Requirements: Complete Compliance Guide

The i-have-adhd repository is released under the MIT License, requiring only that you preserve the copyright notice and full license text in any distribution or modification.

The ayghri/i-have-adhd project is an open-source repository distributed under the permissive MIT License. Understanding the specific MIT license and attribution requirements for i-have-adhd ensures you can legally use, modify, and redistribute the code in personal or commercial projects while maintaining compliance with the author's intellectual property rights.

What the MIT License Permits

The MIT License grants broad freedoms with minimal restrictions. When working with i-have-adhd, you are explicitly permitted to:

• Use the code for any purpose, including commercial applications.
• Modify the source code to suit your specific needs.
• Distribute original or modified versions of the software.
• Sublicense the code to others under the same terms.

These permissions make the MIT License one of the most business-friendly open-source licenses available, allowing integration into proprietary products without complex legal obligations.

Attribution Requirements for i-have-adhd

While the MIT License is permissive, it carries specific attribution obligations that you must satisfy when redistributing the software.

Preserving the LICENSE File

You must retain the original LICENSE file in the root directory of any distribution you publish. This file contains the full MIT license text and the copyright notice Copyright © 2024 ayghri. According to the repository structure, the LICENSE file sits at the repository root and serves as the primary legal document governing all use of the software.

Copyright Notice Obligations

Every copy of the software—whether original or modified—must include the copyright notice. The i-have-adhd repository does not include individual copyright headers in source files, so the global LICENSE file suffices for compliance. If you modify source files, you may add your own copyright notice alongside the original, but you cannot remove or alter the original attribution.

Optional Credit Best Practices

While not legally required by the MIT License, linking to the original repository in your documentation or about page demonstrates good open-source citizenship. The README.md file in the repository root contains the official project reference and License section at the bottom for proper citation.

MIT Compliance Checklist

Ensure your use of i-have-adhd meets all legal requirements with this verification list:

• Include the full MIT license text in every distribution (the LICENSE file).
• Preserve the copyright notice (Copyright © 2024 ayghri).
• If redistributing modified code, you may add your own copyright notice in addition to the original one.
• No obligation exists to disclose your source code or changes.
• Binary distributions do not require source code inclusion, but must still accompany the license text.

Practical Implementation Examples

Implementing MIT compliance correctly depends on your specific use case. The following patterns demonstrate proper attribution for common scenarios.

Including License in npm Packages

When distributing a package that depends on i-have-adhd, copy the license file during your build process to ensure it travels with your distribution:

{
  "name": "my-awesome-tool",
  "version": "1.0.0",
  "license": "MIT",
  "dependencies": {
    "i-have-adhd": "^1.0.0"
  },
  "scripts": {
    "postinstall": "cp node_modules/i-have-adhd/LICENSE ./LICENSE-THIRD-PARTY"
  }
}

This approach satisfies the attribution requirement for third-party dependencies by preserving the original LICENSE alongside your distribution.

Modifying Source Files

When altering i-have-adhd source code, prepend a header that preserves original copyright while adding your own:

/**
 * Modified version of i-have-adhd's main skill.
 *
 * Copyright © 2024 ayghri
 * Copyright © 2026 Your Name
 *
 * Licensed under the MIT License (see LICENSE file for details).
 */
import { skill } from "./i-have-adhd";

This dual-copyright approach acknowledges the original author while claiming rights to your specific modifications.

Displaying Attribution in UI Components

For applications with user interfaces, consider including attribution in your footer:

<footer>
  <p>
    © 2024 ayghri – Licensed under MIT.<br />
    Powered by <a href="https://github.com/ayghri/i-have-adhd">i-have-adhd</a>
  </p>
</footer>

This provides visibility to the original project, though it remains optional under strict MIT terms.

Key Files in the Repository

Understanding the licensing structure requires examining three critical files in ayghri/i-have-adhd:

• LICENSE – Contains the complete MIT license text and required attribution notice. Located at the repository root, this file establishes the legal foundation for all use.
• README.md – Declares the project's license in the License section at the bottom of the document, providing quick reference for contributors and users.
• package.json – Lists "license": "MIT", enabling automated license scanning tools to identify the project's permissions programmatically.

These files collectively define the MIT license and attribution requirements for i-have-adhd, giving you everything needed for compliant usage.

Summary

• The i-have-adhd repository uses the MIT License, permitting unrestricted use, modification, and distribution.
• You must retain the original LICENSE file and copyright notice (Copyright © 2024 ayghri) in all distributions.
• The repository does not require individual file headers; the root LICENSE file satisfies attribution requirements.
• You may add your own copyright to modified versions, but cannot remove the original author's notice.
• No requirement exists to open-source your modifications or provide source code with binary distributions.

Frequently Asked Questions

Do I need to open-source my modifications to i-have-adhd?

No. The MIT License does not impose copyleft requirements. You can modify the code and keep your changes proprietary, provided you include the original copyright notice and license text with your distribution.

Can I use i-have-adhd in a commercial product?

Yes. The MIT License explicitly permits commercial use. You may incorporate the code into proprietary software, sell products built with it, or use it in internal business tools without paying royalties or requesting permission.

Where do I find the official license text?

The official MIT license text resides in the LICENSE file at the root of the ayghri/i-have-adhd repository. The README.md also references the license in its License section, though the LICENSE file contains the complete legal text required for compliance.

What if I modify the source code—do I need to add my own copyright?

You are not required to add your own copyright notice, but you may do so. If you choose to add your name, place it below the original Copyright © 2024 ayghri notice in the LICENSE file or source headers. You cannot remove or alter the original copyright statement.

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