Skip to content
husk
GitHub ↗ Get Husk
§ legal

Acceptable Use Policy

Effective: 2026-04-18

Last updated: 2026-04-18

This Acceptable Use Policy (“AUP”) governs your use of all Mataki Labs LLC (“Husk”) services, products, websites, and infrastructure (the “Services”), including the husk.sh marketing website, the install endpoint at install.husk.sh, and the future Husk Module Registry. This AUP is incorporated by reference into the Terms of Service.

Violation of this AUP may result in suspension or termination of your access to the Services.

1. Prohibited Activities

You may not use the Services to:

1.1 Illegal Activity

  • Violate any applicable law, regulation, or governmental order.
  • Facilitate, promote, or engage in illegal activities, including money laundering, terrorism financing, or trafficking.

1.2 Harmful Content

  • Store, host, or distribute content that is defamatory, libelous, obscene, or that promotes violence or discrimination.
  • Store, host, or distribute material that infringes or misappropriates third-party intellectual property rights.
  • Distribute, host, or transmit malware, viruses, worms, ransomware, spyware, or other malicious code.
  • Store or distribute child sexual abuse material (CSAM). Husk will report any discovered CSAM to the National Center for Missing and Exploited Children (NCMEC) and to law enforcement.

1.3 Abuse and Exploitation

  • Send unsolicited bulk messages (spam) through any Husk-operated channel.
  • Engage in phishing, social engineering, or any deceptive practice intended to obtain credentials, personal information, or financial information.
  • Harvest, scrape, or collect information about other users or visitors without their consent.
  • Interfere with or disrupt the integrity, performance, or availability of the Services, including denial-of-service attacks, resource exhaustion, or intentional overloading.
  • Use automated tools to make requests to the husk.sh website or install endpoint at a rate or scale that degrades service availability for other users.

1.4 Unauthorized Access

  • Access or attempt to access systems or data that you are not authorized to access.
  • Circumvent, disable, or interfere with any security, authentication, or access-control mechanisms of the Services.
  • Reverse engineer, decompile, or disassemble any proprietary part of the Services (this restriction does not apply to open-source components licensed under the Apache License 2.0).
  • Use the Services to probe, scan, or test the vulnerability of any system or network, except with our prior written authorization for legitimate security testing of infrastructure you own or control.

1.5 Install Endpoint Misuse

  • Conduct automated bulk downloads of the installer or release binaries for redistribution without proper attribution to the original source and compliance with the Apache License 2.0.
  • Modify the installer script and distribute it in a manner that could mislead users into believing they are installing the official Husk release.
  • Use the install endpoint in a way that impersonates or misrepresents the source of the Husk language or toolchain.

1.6 Module Registry Violations

The following rules apply to the Husk Module Registry when it becomes available:

  • No typosquatting: Do not register module names that are confusingly similar to well-known modules, standard library components, or popular open-source packages, with the intent to mislead users.
  • No malware: Do not publish modules containing malicious code, supply-chain attack payloads, or code designed to exfiltrate data, damage systems, or interfere with other software without disclosure.
  • No license-incompatible bundling: Do not publish modules that bundle third-party code in a manner incompatible with the bundled code’s license, or that misrepresent the module’s license to end users.
  • No impersonation: Do not publish modules under a name or identity that impersonates another author, organization, or well-known project.
  • Accurate metadata: Module metadata (name, version, description, license, authors) must accurately describe the module. False or misleading metadata is prohibited.

1.7 High-Risk Use

  • Use the Services in any application where failure could lead to death, personal injury, or environmental damage (e.g., medical life-support systems, nuclear facilities, air traffic control) without appropriate contractual safeguards and our prior written authorization.

2. Your Responsibilities

2.1 Compliance with Open-Source Licenses

If you distribute software that incorporates Husk or Husk modules, you are responsible for complying with the applicable open-source licenses, including the Apache License 2.0. You must provide appropriate attribution and comply with all license obligations.

2.2 Module Authors

If you publish modules to the Husk Module Registry (when available), you represent and warrant that:

  • You have all necessary rights to publish the module content.
  • The module does not infringe any third-party intellectual property rights.
  • The module complies with all applicable laws and with this AUP.
  • The module’s stated license accurately reflects its actual license terms.

2.3 Security Reporting

You are responsible for reporting security vulnerabilities you discover in Husk infrastructure responsibly. Do not publicly disclose vulnerabilities before giving us reasonable opportunity to address them. Report security issues to abuse@husk.sh.

3. Enforcement

3.1 Monitoring

Husk does not proactively monitor all activity on the Services for AUP violations. However, Husk may investigate violations that come to its attention through automated systems (e.g., abuse detection), third-party reports, or law enforcement requests.

3.2 Actions

If Husk reasonably determines that a violation of this AUP has occurred or is occurring, Husk may, in its sole discretion:

  • Issue a warning and request that you cease the violating activity.
  • Suspend access to the affected Services, in whole or in part.
  • Remove or disable access to offending content (including unpublishing modules from the registry).
  • Terminate your access to the Services.
  • Report the violation to law enforcement or other appropriate authorities.

3.3 Notice

Except where immediate action is reasonably necessary to protect the Services, other users, or third parties, Husk will provide you with reasonable notice and an opportunity to cure before taking enforcement action. Where immediate action is taken, Husk will notify you as soon as practicable thereafter.

3.4 No Obligation

Husk has no obligation to enforce this AUP against other users on your behalf. This AUP does not create any obligation for Husk to monitor or police use of the Services.

4. Reporting Violations

If you become aware of a violation of this AUP, please report it to abuse@husk.sh. Reports should include: the nature of the violation, the resource or module involved (if known), and any supporting evidence.

For DMCA copyright notices, see the Terms of Service.

5. Community Conduct

Use of Husk’s GitHub repositories, issue trackers, and any community channels (Discord, forums, etc.) is also subject to the Husk community Code of Conduct, published in the GitHub repository. The Code of Conduct governs interpersonal conduct; this AUP governs use of the technical infrastructure.

6. Changes to This Policy

Husk may update this AUP from time to time. We will notify you of material changes at least thirty (30) days in advance by posting the updated policy on this page and updating the effective date. Your continued use of the Services after the effective date constitutes acceptance of the updated AUP.

7. Contact

Questions about this AUP should be directed to:

Mataki Labs LLC State of Wyoming Email: abuse@husk.sh