From f1387e27286d05da706f8d73aafbd77164967e07 Mon Sep 17 00:00:00 2001 From: Marko Vejnovic Date: Thu, 9 Jul 2026 03:51:38 +0000 Subject: [PATCH 1/8] docs(cla): replace copyright assignment with non-exclusive license grant --- CLA.md | 41 +++++++++++++++++++++++------------------ 1 file changed, 23 insertions(+), 18 deletions(-) diff --git a/CLA.md b/CLA.md index d2b4de3b..6ce46274 100644 --- a/CLA.md +++ b/CLA.md @@ -6,7 +6,8 @@ Thank you for your interest in contributing to Hyper (the "Project"). This Contributor License Agreement ("Agreement") sets out the terms under which contributions are accepted. It protects both you ("Contributor") and the Owner, -and it keeps the Project's copyright consolidated under a single holder. +and it gives the Owner the licensing rights needed to sustain, relicense, and +dual-license the Project — without asking you to give up ownership of your work. By submitting a Contribution to the Project (for example, by opening a pull request, sending a patch, or pushing a commit), you agree to the terms below. @@ -22,27 +23,31 @@ If you do not agree, do not submit a Contribution. and electronic communication), excluding any communication conspicuously marked in writing as "Not a Contribution." -## 2. Copyright Assignment +## 2. License Grant -You hereby assign, transfer, and convey to the Owner all right, title, and -interest worldwide in all copyright in your Contribution, including the right -to sue for and recover damages for past, present, and future infringement. To -the extent any such assignment is unenforceable in a given jurisdiction, you -instead grant the Owner an exclusive, perpetual, irrevocable, worldwide, -royalty-free, transferable, and sublicensable license to use, reproduce, -modify, distribute, publicly perform and display, sublicense, and create -derivative works of your Contribution, and to relicense or dual-license it -under any terms the Owner chooses. +You retain all right, title, and interest in the copyright to your +Contribution. You do **not** assign or transfer ownership of your Contribution +to the Owner. -As a result, the Owner remains the sole copyright holder of the Project and may -license, relicense, or dual-license the Project — including the AGPL-3.0-or-later -license under which it is currently distributed — at the Owner's sole discretion. +You hereby grant to the Owner a perpetual, worldwide, non-exclusive, +royalty-free, irrevocable, and transferable license — with the right to grant +and authorize sublicenses through multiple tiers of sublicensees — to use, +reproduce, modify, adapt, publicly perform and display, distribute, and create +derivative works of your Contribution, and to relicense and dual-license your +Contribution (alone or as part of the Project) under any terms the Owner +chooses, including proprietary or commercial terms. -## 3. License Back to Contributor +Because this grant is non-exclusive, the Owner may license, relicense, or +dual-license the Project — including the AGPL-3.0-or-later license under which +it is currently distributed — at the Owner's sole discretion, while you keep +every right you hold as the copyright owner of your own Contribution. -The Owner grants back to you a non-exclusive, perpetual, irrevocable, -worldwide, royalty-free license to use your own Contribution for any purpose. -You are not restricted from using the work you authored. +## 3. Your Retained Rights + +You retain ownership of the copyright in your Contribution. Nothing in this +Agreement restricts you from using, licensing, relicensing, or otherwise +exploiting the work you authored for any purpose. The license you grant in +Section 2 is non-exclusive and coexists with every right you keep as the owner. ## 4. Patent License From dfdc0201013cff0a1c3a00f396f44833abb32178 Mon Sep 17 00:00:00 2001 From: Marko Vejnovic Date: Thu, 9 Jul 2026 03:54:02 +0000 Subject: [PATCH 2/8] =?UTF-8?q?docs(cla):=20align=20=C2=A75=20representati?= =?UTF-8?q?on=20with=20license-grant=20model?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- CLA.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CLA.md b/CLA.md index 6ce46274..d29c941b 100644 --- a/CLA.md +++ b/CLA.md @@ -63,7 +63,7 @@ Contribution with the Project. You represent that: 1. Each Contribution is an original work that you created, and you have the - legal right to assign the rights set out above. + legal right to grant the license set out above. 2. If your employer has rights to intellectual property you create, you have either received permission to make the Contribution on behalf of that employer, or your employer has waived such rights for the Contribution. From 8e8782dfa341f68909d99a0ae6ff31058b51740a Mon Sep 17 00:00:00 2001 From: Marko Vejnovic Date: Thu, 9 Jul 2026 03:55:10 +0000 Subject: [PATCH 3/8] docs(cla): reword NOTICE contributor clause to license grant --- NOTICE | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/NOTICE b/NOTICE index 3e410ce1..caa9723b 100644 --- a/NOTICE +++ b/NOTICE @@ -14,12 +14,13 @@ repository, and also available at . ---------------------------------------------------------------------------- -COPYRIGHT ASSIGNMENT +CONTRIBUTOR LICENSE All contributions to this project are governed by the Contributor License Agreement in CLA.md. By submitting a contribution (a patch, pull request, or -any other form), you assign your copyright in that contribution to Marko -Vejnovic, who remains the sole copyright holder of this project. This -assignment exists so the copyright can be enforced from a single owner and so -the project may be relicensed or dual-licensed in the future at the owner's -discretion. See CLA.md for the full terms. +any other form), you keep the copyright to your contribution and grant Marko +Vejnovic a perpetual, worldwide, non-exclusive, sublicensable license to use it +and to relicense or dual-license it as part of the project. This lets the +copyright be enforced from, and the project be relicensed by, a single party +without asking contributors to give up ownership of their work. See CLA.md for +the full terms. From 86af480cc76f379b50b4fab33990a65471c8ff81 Mon Sep 17 00:00:00 2001 From: Marko Vejnovic Date: Thu, 9 Jul 2026 03:57:41 +0000 Subject: [PATCH 4/8] docs(cla): reframe CONTRIBUTING CLA rationale as license, not assignment --- CONTRIBUTING.md | 32 +++++++++++++++++--------------- 1 file changed, 17 insertions(+), 15 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 06d31e88..49f8926c 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -7,12 +7,12 @@ bar and a few non-obvious requirements. ## Before you start By submitting a contribution (a pull request, patch, or commit) you agree to -the [Contributor License Agreement](CLA.md). In short: **you assign copyright -in your contribution to the project owner**, who keeps the copyright -consolidated so Hyper can be relicensed or dual-licensed in the future. You -retain a perpetual license to your own work. If you are contributing on company -time, make sure you have permission to do so. If you do not agree with the CLA, -please do not submit a contribution. +the [Contributor License Agreement](CLA.md). In short: **you keep the copyright +to your contribution** and grant the project owner a broad, non-exclusive +license — including the right to relicense and dual-license Hyper in the +future. You are not asked to give up ownership of your work. If you are +contributing on company time, make sure you have permission to do so. If you do +not agree with the CLA, please do not submit a contribution. For anything beyond a small fix, **open an issue first** and describe what you intend to do. Hyper is opinionated and moves fast; a quick discussion avoids @@ -27,22 +27,24 @@ compatible. Under the AGPL, every contributor owns the copyright to their own patches. That sounds nice, but it means the license can never be changed without tracking down and getting agreement from every person who ever contributed -- the same reason -Linux can never move off GPLv2. Consolidating copyright under a single owner -avoids that trap and lets Hyper: +Linux can never move off GPLv2. The CLA sidesteps that trap **without taking +your copyright**: you keep ownership, and you grant the owner a broad, +non-exclusive, sublicensable license. That single grant is enough to let Hyper: - **Relicense in the future** if the AGPL stops serving the project. - **Offer commercial licenses** to organizations that cannot use AGPL code, - which is how development gets funded. You can only sell what you wholly own. -- **Enforce the license** against infringers without coordinating dozens of - copyright holders. + which is how development gets funded. A sublicensable license lets the owner + do this without owning your copyright outright. +- **Enforce the license** against infringers from a single party, without + coordinating dozens of copyright holders. Yes, this is asymmetric: the owner reserves the right to license Hyper proprietarily, which the AGPL denies everyone else. That is the deal open-core -projects make, and we would rather state it plainly than bury it. In exchange, -the CLA grants you a perpetual license to keep using your own contributions for -any purpose (CLA §3) -- you never lose the right to the work you authored. +projects make, and we would rather state it plainly than bury it. But you are +not signing your work away -- you keep the copyright to everything you author +(CLA §3) and stay free to use it however you like. -If assigning copyright is not something you are willing to do, that is a +If granting that license is not something you are willing to do, that is a completely reasonable position -- but please do not submit a contribution. ## What we are looking for From afb760ed48bcc7c4c6872d1636bcfeeaf8c71d2a Mon Sep 17 00:00:00 2001 From: Marko Vejnovic Date: Thu, 9 Jul 2026 04:01:23 +0000 Subject: [PATCH 5/8] docs(cla): update README contributing note to license grant --- README.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 7b2361f1..9494514c 100644 --- a/README.md +++ b/README.md @@ -127,10 +127,11 @@ quality gate (`mix check` must pass) and a few Linux/Firecracker prerequisites. Read [CONTRIBUTING.md](CONTRIBUTING.md) before opening a pull request. Note that all contributions are governed by the -[Contributor License Agreement](CLA.md): by submitting a PR you assign -copyright in your contribution to the project owner, which keeps Hyper's -copyright consolidated. If that is a dealbreaker for you, it is better to know -up front. +[Contributor License Agreement](CLA.md): by submitting a PR you keep the +copyright to your contribution and grant the project owner a broad, +non-exclusive license (including the right to relicense and dual-license +Hyper). You are not asked to give up ownership. If that is a dealbreaker for +you, it is better to know up front. ## License From 0fac074127b3e0e0790a70a0647fd235b22805a9 Mon Sep 17 00:00:00 2001 From: Marko Vejnovic Date: Thu, 9 Jul 2026 04:05:36 +0000 Subject: [PATCH 6/8] docs(cla): drop enforcement over-claim inconsistent with non-exclusive grant --- CONTRIBUTING.md | 4 ++-- NOTICE | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 49f8926c..6abce035 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -35,8 +35,8 @@ non-exclusive, sublicensable license. That single grant is enough to let Hyper: - **Offer commercial licenses** to organizations that cannot use AGPL code, which is how development gets funded. A sublicensable license lets the owner do this without owning your copyright outright. -- **Enforce the license** against infringers from a single party, without - coordinating dozens of copyright holders. +- **Keep licensing decisions consolidated** in a single party, so the + project's terms can evolve without coordinating dozens of copyright holders. Yes, this is asymmetric: the owner reserves the right to license Hyper proprietarily, which the AGPL denies everyone else. That is the deal open-core diff --git a/NOTICE b/NOTICE index caa9723b..ed0d264f 100644 --- a/NOTICE +++ b/NOTICE @@ -21,6 +21,6 @@ Agreement in CLA.md. By submitting a contribution (a patch, pull request, or any other form), you keep the copyright to your contribution and grant Marko Vejnovic a perpetual, worldwide, non-exclusive, sublicensable license to use it and to relicense or dual-license it as part of the project. This lets the -copyright be enforced from, and the project be relicensed by, a single party -without asking contributors to give up ownership of their work. See CLA.md for +project be relicensed and dual-licensed by a single party without asking +contributors to give up ownership of their work. See CLA.md for the full terms. From 94833bd2d8bbce8e3b51de7f588a65505cb34a0b Mon Sep 17 00:00:00 2001 From: Marko Vejnovic Date: Thu, 9 Jul 2026 04:12:20 +0000 Subject: [PATCH 7/8] chore: relicense from AGPL-3.0-or-later to MIT Replace the AGPL LICENSE with the MIT License, flip all SPDX headers (18 suidhelper source files) and Cargo.toml/mix.exs license fields to MIT, and update the README license/contributing sections plus .devin/wiki.json. Drop the Contributor License Agreement: under MIT the dual-licensing rationale is moot, so contributions are accepted inbound=outbound with contributors retaining copyright. Deletes CLA.md and the AGPL NOTICE file and removes their references. --- .devin/wiki.json | 2 +- CLA.md | 88 --- CONTRIBUTING.md | 41 +- LICENSE | 682 +----------------- NOTICE | 26 - README.md | 38 +- mix.exs | 4 +- native/suidhelper/Cargo.toml | 2 +- native/suidhelper/build.rs | 2 +- native/suidhelper/meta/Cargo.toml | 2 +- native/suidhelper/src/config.rs | 2 +- native/suidhelper/src/security_gate.rs | 2 +- .../suidhelper/src/tools/chroot_jail/grant.rs | 2 +- .../src/tools/chroot_jail/grant_api.rs | 2 +- .../src/tools/chroot_jail/grant_vsock.rs | 2 +- .../suidhelper/src/tools/chroot_jail/mod.rs | 2 +- .../src/tools/chroot_jail/prepare.rs | 2 +- .../src/tools/chroot_jail/remove.rs | 2 +- native/suidhelper/src/tools/jailer.rs | 2 +- native/suidhelper/src/tools/network/mod.rs | 2 +- native/suidhelper/src/util/chroot_jail.rs | 2 +- native/suidhelper/src/util/jailer.rs | 2 +- native/suidhelper/src/util/path.rs | 2 +- native/suidhelper/src/util/safe_dev.rs | 2 +- native/suidhelper/src/util/safe_dir.rs | 2 +- native/suidhelper/src/util/safe_file.rs | 2 +- native/suidhelper/src/util/safe_path.rs | 2 +- 27 files changed, 57 insertions(+), 864 deletions(-) delete mode 100644 CLA.md delete mode 100644 NOTICE diff --git a/.devin/wiki.json b/.devin/wiki.json index 570a8b8b..9514a75d 100644 --- a/.devin/wiki.json +++ b/.devin/wiki.json @@ -17,7 +17,7 @@ "author": "Marko Vejnovic" }, { - "content": "Canonical operator documentation lives in docs/cookbook/ (especially install.md for host provisioning: KVM, device-mapper thin pools, the setuid helper) and is published to https://hexdocs.pm/hypervm/. Prefer citing those guides for installation and configuration rather than inferring procedures from code. The package is published on Hex as `hypervm`. License is AGPL-3.0-or-later.", + "content": "Canonical operator documentation lives in docs/cookbook/ (especially install.md for host provisioning: KVM, device-mapper thin pools, the setuid helper) and is published to https://hexdocs.pm/hypervm/. Prefer citing those guides for installation and configuration rather than inferring procedures from code. The package is published on Hex as `hypervm`. License is MIT.", "author": "Marko Vejnovic" } ] diff --git a/CLA.md b/CLA.md deleted file mode 100644 index d29c941b..00000000 --- a/CLA.md +++ /dev/null @@ -1,88 +0,0 @@ -# Contributor License Agreement - -**Project:** Hyper -**Copyright holder ("Owner"):** Marko Vejnovic <marko@harmont.dev> - -Thank you for your interest in contributing to Hyper (the "Project"). This -Contributor License Agreement ("Agreement") sets out the terms under which -contributions are accepted. It protects both you ("Contributor") and the Owner, -and it gives the Owner the licensing rights needed to sustain, relicense, and -dual-license the Project — without asking you to give up ownership of your work. - -By submitting a Contribution to the Project (for example, by opening a pull -request, sending a patch, or pushing a commit), you agree to the terms below. -If you do not agree, do not submit a Contribution. - -## 1. Definitions - -- **"Contribution"** means any original work of authorship — including any - modification to, or addition to, existing work — that you intentionally - submit to the Project in any form. -- **"Submit"** means any form of communication sent to the Owner or the - Project (including but not limited to source code, pull requests, issues, - and electronic communication), excluding any communication conspicuously - marked in writing as "Not a Contribution." - -## 2. License Grant - -You retain all right, title, and interest in the copyright to your -Contribution. You do **not** assign or transfer ownership of your Contribution -to the Owner. - -You hereby grant to the Owner a perpetual, worldwide, non-exclusive, -royalty-free, irrevocable, and transferable license — with the right to grant -and authorize sublicenses through multiple tiers of sublicensees — to use, -reproduce, modify, adapt, publicly perform and display, distribute, and create -derivative works of your Contribution, and to relicense and dual-license your -Contribution (alone or as part of the Project) under any terms the Owner -chooses, including proprietary or commercial terms. - -Because this grant is non-exclusive, the Owner may license, relicense, or -dual-license the Project — including the AGPL-3.0-or-later license under which -it is currently distributed — at the Owner's sole discretion, while you keep -every right you hold as the copyright owner of your own Contribution. - -## 3. Your Retained Rights - -You retain ownership of the copyright in your Contribution. Nothing in this -Agreement restricts you from using, licensing, relicensing, or otherwise -exploiting the work you authored for any purpose. The license you grant in -Section 2 is non-exclusive and coexists with every right you keep as the owner. - -## 4. Patent License - -You grant the Owner and all recipients of the Project a perpetual, worldwide, -non-exclusive, royalty-free, irrevocable patent license to make, have made, -use, offer to sell, sell, import, and otherwise transfer your Contribution, -where such license applies only to those patent claims licensable by you that -are necessarily infringed by your Contribution alone or by combination of your -Contribution with the Project. - -## 5. Your Representations - -You represent that: - -1. Each Contribution is an original work that you created, and you have the - legal right to grant the license set out above. -2. If your employer has rights to intellectual property you create, you have - either received permission to make the Contribution on behalf of that - employer, or your employer has waived such rights for the Contribution. -3. Your Contribution does not, to your knowledge, violate any third party's - copyright, patent, trademark, trade secret, or other rights. -4. Your Contribution is provided without any warranty, express or implied, - except as stated in this Agreement. - -## 6. Governing Law - -This Agreement is governed by and construed in accordance with the laws of the -State of California, United States, without regard to its conflict-of-law -provisions. Any dispute arising out of or relating to this Agreement shall be -subject to the exclusive jurisdiction of the state and federal courts located -in California. - -## 7. Miscellaneous - -This Agreement is the entire agreement concerning Contributions and supersedes -any prior agreement on the subject. If any provision is held unenforceable, the -remaining provisions remain in effect. This Agreement does not obligate the -Owner to use or incorporate any Contribution. diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 6abce035..7f4356c4 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -6,47 +6,16 @@ bar and a few non-obvious requirements. ## Before you start -By submitting a contribution (a pull request, patch, or commit) you agree to -the [Contributor License Agreement](CLA.md). In short: **you keep the copyright -to your contribution** and grant the project owner a broad, non-exclusive -license — including the right to relicense and dual-license Hyper in the -future. You are not asked to give up ownership of your work. If you are -contributing on company time, make sure you have permission to do so. If you do -not agree with the CLA, please do not submit a contribution. +Hyper is licensed under the MIT License. By submitting a contribution (a pull +request, patch, or commit) you agree that it is licensed to the project under +those same terms; you retain the copyright to your own work. There is no +separate contributor license agreement to sign. If you are contributing on +company time, make sure you have permission to do so. For anything beyond a small fix, **open an issue first** and describe what you intend to do. Hyper is opinionated and moves fast; a quick discussion avoids wasted work on a PR that does not fit the direction of the project. -### Why a CLA? - -Hyper is released under the AGPL, but it is also the commercial backbone of -[harmont.dev](https://harmont.dev). The CLA exists to keep those two facts -compatible. - -Under the AGPL, every contributor owns the copyright to their own patches. That -sounds nice, but it means the license can never be changed without tracking down -and getting agreement from every person who ever contributed -- the same reason -Linux can never move off GPLv2. The CLA sidesteps that trap **without taking -your copyright**: you keep ownership, and you grant the owner a broad, -non-exclusive, sublicensable license. That single grant is enough to let Hyper: - -- **Relicense in the future** if the AGPL stops serving the project. -- **Offer commercial licenses** to organizations that cannot use AGPL code, - which is how development gets funded. A sublicensable license lets the owner - do this without owning your copyright outright. -- **Keep licensing decisions consolidated** in a single party, so the - project's terms can evolve without coordinating dozens of copyright holders. - -Yes, this is asymmetric: the owner reserves the right to license Hyper -proprietarily, which the AGPL denies everyone else. That is the deal open-core -projects make, and we would rather state it plainly than bury it. But you are -not signing your work away -- you keep the copyright to everything you author -(CLA §3) and stay free to use it however you like. - -If granting that license is not something you are willing to do, that is a -completely reasonable position -- but please do not submit a contribution. - ## What we are looking for - **Bug fixes** with a clear reproduction. diff --git a/LICENSE b/LICENSE index be3f7b28..d3f90b36 100644 --- a/LICENSE +++ b/LICENSE @@ -1,661 +1,21 @@ - GNU AFFERO GENERAL PUBLIC LICENSE - Version 3, 19 November 2007 - - Copyright (C) 2007 Free Software Foundation, Inc. - Everyone is permitted to copy and distribute verbatim copies - of this license document, but changing it is not allowed. - - Preamble - - The GNU Affero General Public License is a free, copyleft license for -software and other kinds of works, specifically designed to ensure -cooperation with the community in the case of network server software. - - The licenses for most software and other practical works are designed -to take away your freedom to share and change the works. By contrast, -our General Public Licenses are intended to guarantee your freedom to -share and change all versions of a program--to make sure it remains free -software for all its users. - - When we speak of free software, we are referring to freedom, not -price. Our General Public Licenses are designed to make sure that you -have the freedom to distribute copies of free software (and charge for -them if you wish), that you receive source code or can get it if you -want it, that you can change the software or use pieces of it in new -free programs, and that you know you can do these things. - - Developers that use our General Public Licenses protect your rights -with two steps: (1) assert copyright on the software, and (2) offer -you this License which gives you legal permission to copy, distribute -and/or modify the software. - - A secondary benefit of defending all users' freedom is that -improvements made in alternate versions of the program, if they -receive widespread use, become available for other developers to -incorporate. Many developers of free software are heartened and -encouraged by the resulting cooperation. However, in the case of -software used on network servers, this result may fail to come about. -The GNU General Public License permits making a modified version and -letting the public access it on a server without ever releasing its -source code to the public. - - The GNU Affero General Public License is designed specifically to -ensure that, in such cases, the modified source code becomes available -to the community. It requires the operator of a network server to -provide the source code of the modified version running there to the -users of that server. Therefore, public use of a modified version, on -a publicly accessible server, gives the public access to the source -code of the modified version. - - An older license, called the Affero General Public License and -published by Affero, was designed to accomplish similar goals. This is -a different license, not a version of the Affero GPL, but Affero has -released a new version of the Affero GPL which permits relicensing under -this license. - - The precise terms and conditions for copying, distribution and -modification follow. - - TERMS AND CONDITIONS - - 0. Definitions. - - "This License" refers to version 3 of the GNU Affero General Public License. - - "Copyright" also means copyright-like laws that apply to other kinds of -works, such as semiconductor masks. - - "The Program" refers to any copyrightable work licensed under this -License. Each licensee is addressed as "you". "Licensees" and -"recipients" may be individuals or organizations. - - To "modify" a work means to copy from or adapt all or part of the work -in a fashion requiring copyright permission, other than the making of an -exact copy. The resulting work is called a "modified version" of the -earlier work or a work "based on" the earlier work. - - A "covered work" means either the unmodified Program or a work based -on the Program. - - To "propagate" a work means to do anything with it that, without -permission, would make you directly or secondarily liable for -infringement under applicable copyright law, except executing it on a -computer or modifying a private copy. Propagation includes copying, -distribution (with or without modification), making available to the -public, and in some countries other activities as well. - - To "convey" a work means any kind of propagation that enables other -parties to make or receive copies. Mere interaction with a user through -a computer network, with no transfer of a copy, is not conveying. - - An interactive user interface displays "Appropriate Legal Notices" -to the extent that it includes a convenient and prominently visible -feature that (1) displays an appropriate copyright notice, and (2) -tells the user that there is no warranty for the work (except to the -extent that warranties are provided), that licensees may convey the -work under this License, and how to view a copy of this License. If -the interface presents a list of user commands or options, such as a -menu, a prominent item in the list meets this criterion. - - 1. Source Code. - - The "source code" for a work means the preferred form of the work -for making modifications to it. "Object code" means any non-source -form of a work. - - A "Standard Interface" means an interface that either is an official -standard defined by a recognized standards body, or, in the case of -interfaces specified for a particular programming language, one that -is widely used among developers working in that language. - - The "System Libraries" of an executable work include anything, other -than the work as a whole, that (a) is included in the normal form of -packaging a Major Component, but which is not part of that Major -Component, and (b) serves only to enable use of the work with that -Major Component, or to implement a Standard Interface for which an -implementation is available to the public in source code form. A -"Major Component", in this context, means a major essential component -(kernel, window system, and so on) of the specific operating system -(if any) on which the executable work runs, or a compiler used to -produce the work, or an object code interpreter used to run it. - - The "Corresponding Source" for a work in object code form means all -the source code needed to generate, install, and (for an executable -work) run the object code and to modify the work, including scripts to -control those activities. However, it does not include the work's -System Libraries, or general-purpose tools or generally available free -programs which are used unmodified in performing those activities but -which are not part of the work. For example, Corresponding Source -includes interface definition files associated with source files for -the work, and the source code for shared libraries and dynamically -linked subprograms that the work is specifically designed to require, -such as by intimate data communication or control flow between those -subprograms and other parts of the work. - - The Corresponding Source need not include anything that users -can regenerate automatically from other parts of the Corresponding -Source. - - The Corresponding Source for a work in source code form is that -same work. - - 2. Basic Permissions. - - All rights granted under this License are granted for the term of -copyright on the Program, and are irrevocable provided the stated -conditions are met. This License explicitly affirms your unlimited -permission to run the unmodified Program. The output from running a -covered work is covered by this License only if the output, given its -content, constitutes a covered work. This License acknowledges your -rights of fair use or other equivalent, as provided by copyright law. - - You may make, run and propagate covered works that you do not -convey, without conditions so long as your license otherwise remains -in force. You may convey covered works to others for the sole purpose -of having them make modifications exclusively for you, or provide you -with facilities for running those works, provided that you comply with -the terms of this License in conveying all material for which you do -not control copyright. Those thus making or running the covered works -for you must do so exclusively on your behalf, under your direction -and control, on terms that prohibit them from making any copies of -your copyrighted material outside their relationship with you. - - Conveying under any other circumstances is permitted solely under -the conditions stated below. Sublicensing is not allowed; section 10 -makes it unnecessary. - - 3. Protecting Users' Legal Rights From Anti-Circumvention Law. - - No covered work shall be deemed part of an effective technological -measure under any applicable law fulfilling obligations under article -11 of the WIPO copyright treaty adopted on 20 December 1996, or -similar laws prohibiting or restricting circumvention of such -measures. - - When you convey a covered work, you waive any legal power to forbid -circumvention of technological measures to the extent such circumvention -is effected by exercising rights under this License with respect to -the covered work, and you disclaim any intention to limit operation or -modification of the work as a means of enforcing, against the work's -users, your or third parties' legal rights to forbid circumvention of -technological measures. - - 4. Conveying Verbatim Copies. - - You may convey verbatim copies of the Program's source code as you -receive it, in any medium, provided that you conspicuously and -appropriately publish on each copy an appropriate copyright notice; -keep intact all notices stating that this License and any -non-permissive terms added in accord with section 7 apply to the code; -keep intact all notices of the absence of any warranty; and give all -recipients a copy of this License along with the Program. - - You may charge any price or no price for each copy that you convey, -and you may offer support or warranty protection for a fee. - - 5. Conveying Modified Source Versions. - - You may convey a work based on the Program, or the modifications to -produce it from the Program, in the form of source code under the -terms of section 4, provided that you also meet all of these conditions: - - a) The work must carry prominent notices stating that you modified - it, and giving a relevant date. - - b) The work must carry prominent notices stating that it is - released under this License and any conditions added under section - 7. This requirement modifies the requirement in section 4 to - "keep intact all notices". - - c) You must license the entire work, as a whole, under this - License to anyone who comes into possession of a copy. This - License will therefore apply, along with any applicable section 7 - additional terms, to the whole of the work, and all its parts, - regardless of how they are packaged. This License gives no - permission to license the work in any other way, but it does not - invalidate such permission if you have separately received it. - - d) If the work has interactive user interfaces, each must display - Appropriate Legal Notices; however, if the Program has interactive - interfaces that do not display Appropriate Legal Notices, your - work need not make them do so. - - A compilation of a covered work with other separate and independent -works, which are not by their nature extensions of the covered work, -and which are not combined with it such as to form a larger program, -in or on a volume of a storage or distribution medium, is called an -"aggregate" if the compilation and its resulting copyright are not -used to limit the access or legal rights of the compilation's users -beyond what the individual works permit. Inclusion of a covered work -in an aggregate does not cause this License to apply to the other -parts of the aggregate. - - 6. Conveying Non-Source Forms. - - You may convey a covered work in object code form under the terms -of sections 4 and 5, provided that you also convey the -machine-readable Corresponding Source under the terms of this License, -in one of these ways: - - a) Convey the object code in, or embodied in, a physical product - (including a physical distribution medium), accompanied by the - Corresponding Source fixed on a durable physical medium - customarily used for software interchange. - - b) Convey the object code in, or embodied in, a physical product - (including a physical distribution medium), accompanied by a - written offer, valid for at least three years and valid for as - long as you offer spare parts or customer support for that product - model, to give anyone who possesses the object code either (1) a - copy of the Corresponding Source for all the software in the - product that is covered by this License, on a durable physical - medium customarily used for software interchange, for a price no - more than your reasonable cost of physically performing this - conveying of source, or (2) access to copy the - Corresponding Source from a network server at no charge. - - c) Convey individual copies of the object code with a copy of the - written offer to provide the Corresponding Source. This - alternative is allowed only occasionally and noncommercially, and - only if you received the object code with such an offer, in accord - with subsection 6b. - - d) Convey the object code by offering access from a designated - place (gratis or for a charge), and offer equivalent access to the - Corresponding Source in the same way through the same place at no - further charge. You need not require recipients to copy the - Corresponding Source along with the object code. If the place to - copy the object code is a network server, the Corresponding Source - may be on a different server (operated by you or a third party) - that supports equivalent copying facilities, provided you maintain - clear directions next to the object code saying where to find the - Corresponding Source. Regardless of what server hosts the - Corresponding Source, you remain obligated to ensure that it is - available for as long as needed to satisfy these requirements. - - e) Convey the object code using peer-to-peer transmission, provided - you inform other peers where the object code and Corresponding - Source of the work are being offered to the general public at no - charge under subsection 6d. - - A separable portion of the object code, whose source code is excluded -from the Corresponding Source as a System Library, need not be -included in conveying the object code work. - - A "User Product" is either (1) a "consumer product", which means any -tangible personal property which is normally used for personal, family, -or household purposes, or (2) anything designed or sold for incorporation -into a dwelling. In determining whether a product is a consumer product, -doubtful cases shall be resolved in favor of coverage. For a particular -product received by a particular user, "normally used" refers to a -typical or common use of that class of product, regardless of the status -of the particular user or of the way in which the particular user -actually uses, or expects or is expected to use, the product. A product -is a consumer product regardless of whether the product has substantial -commercial, industrial or non-consumer uses, unless such uses represent -the only significant mode of use of the product. - - "Installation Information" for a User Product means any methods, -procedures, authorization keys, or other information required to install -and execute modified versions of a covered work in that User Product from -a modified version of its Corresponding Source. The information must -suffice to ensure that the continued functioning of the modified object -code is in no case prevented or interfered with solely because -modification has been made. - - If you convey an object code work under this section in, or with, or -specifically for use in, a User Product, and the conveying occurs as -part of a transaction in which the right of possession and use of the -User Product is transferred to the recipient in perpetuity or for a -fixed term (regardless of how the transaction is characterized), the -Corresponding Source conveyed under this section must be accompanied -by the Installation Information. But this requirement does not apply -if neither you nor any third party retains the ability to install -modified object code on the User Product (for example, the work has -been installed in ROM). - - The requirement to provide Installation Information does not include a -requirement to continue to provide support service, warranty, or updates -for a work that has been modified or installed by the recipient, or for -the User Product in which it has been modified or installed. Access to a -network may be denied when the modification itself materially and -adversely affects the operation of the network or violates the rules and -protocols for communication across the network. - - Corresponding Source conveyed, and Installation Information provided, -in accord with this section must be in a format that is publicly -documented (and with an implementation available to the public in -source code form), and must require no special password or key for -unpacking, reading or copying. - - 7. Additional Terms. - - "Additional permissions" are terms that supplement the terms of this -License by making exceptions from one or more of its conditions. -Additional permissions that are applicable to the entire Program shall -be treated as though they were included in this License, to the extent -that they are valid under applicable law. If additional permissions -apply only to part of the Program, that part may be used separately -under those permissions, but the entire Program remains governed by -this License without regard to the additional permissions. - - When you convey a copy of a covered work, you may at your option -remove any additional permissions from that copy, or from any part of -it. (Additional permissions may be written to require their own -removal in certain cases when you modify the work.) You may place -additional permissions on material, added by you to a covered work, -for which you have or can give appropriate copyright permission. - - Notwithstanding any other provision of this License, for material you -add to a covered work, you may (if authorized by the copyright holders of -that material) supplement the terms of this License with terms: - - a) Disclaiming warranty or limiting liability differently from the - terms of sections 15 and 16 of this License; or - - b) Requiring preservation of specified reasonable legal notices or - author attributions in that material or in the Appropriate Legal - Notices displayed by works containing it; or - - c) Prohibiting misrepresentation of the origin of that material, or - requiring that modified versions of such material be marked in - reasonable ways as different from the original version; or - - d) Limiting the use for publicity purposes of names of licensors or - authors of the material; or - - e) Declining to grant rights under trademark law for use of some - trade names, trademarks, or service marks; or - - f) Requiring indemnification of licensors and authors of that - material by anyone who conveys the material (or modified versions of - it) with contractual assumptions of liability to the recipient, for - any liability that these contractual assumptions directly impose on - those licensors and authors. - - All other non-permissive additional terms are considered "further -restrictions" within the meaning of section 10. If the Program as you -received it, or any part of it, contains a notice stating that it is -governed by this License along with a term that is a further -restriction, you may remove that term. If a license document contains -a further restriction but permits relicensing or conveying under this -License, you may add to a covered work material governed by the terms -of that license document, provided that the further restriction does -not survive such relicensing or conveying. - - If you add terms to a covered work in accord with this section, you -must place, in the relevant source files, a statement of the -additional terms that apply to those files, or a notice indicating -where to find the applicable terms. - - Additional terms, permissive or non-permissive, may be stated in the -form of a separately written license, or stated as exceptions; -the above requirements apply either way. - - 8. Termination. - - You may not propagate or modify a covered work except as expressly -provided under this License. Any attempt otherwise to propagate or -modify it is void, and will automatically terminate your rights under -this License (including any patent licenses granted under the third -paragraph of section 11). - - However, if you cease all violation of this License, then your -license from a particular copyright holder is reinstated (a) -provisionally, unless and until the copyright holder explicitly and -finally terminates your license, and (b) permanently, if the copyright -holder fails to notify you of the violation by some reasonable means -prior to 60 days after the cessation. - - Moreover, your license from a particular copyright holder is -reinstated permanently if the copyright holder notifies you of the -violation by some reasonable means, this is the first time you have -received notice of violation of this License (for any work) from that -copyright holder, and you cure the violation prior to 30 days after -your receipt of the notice. - - Termination of your rights under this section does not terminate the -licenses of parties who have received copies or rights from you under -this License. If your rights have been terminated and not permanently -reinstated, you do not qualify to receive new licenses for the same -material under section 10. - - 9. Acceptance Not Required for Having Copies. - - You are not required to accept this License in order to receive or -run a copy of the Program. Ancillary propagation of a covered work -occurring solely as a consequence of using peer-to-peer transmission -to receive a copy likewise does not require acceptance. However, -nothing other than this License grants you permission to propagate or -modify any covered work. These actions infringe copyright if you do -not accept this License. Therefore, by modifying or propagating a -covered work, you indicate your acceptance of this License to do so. - - 10. Automatic Licensing of Downstream Recipients. - - Each time you convey a covered work, the recipient automatically -receives a license from the original licensors, to run, modify and -propagate that work, subject to this License. You are not responsible -for enforcing compliance by third parties with this License. - - An "entity transaction" is a transaction transferring control of an -organization, or substantially all assets of one, or subdividing an -organization, or merging organizations. If propagation of a covered -work results from an entity transaction, each party to that -transaction who receives a copy of the work also receives whatever -licenses to the work the party's predecessor in interest had or could -give under the previous paragraph, plus a right to possession of the -Corresponding Source of the work from the predecessor in interest, if -the predecessor has it or can get it with reasonable efforts. - - You may not impose any further restrictions on the exercise of the -rights granted or affirmed under this License. For example, you may -not impose a license fee, royalty, or other charge for exercise of -rights granted under this License, and you may not initiate litigation -(including a cross-claim or counterclaim in a lawsuit) alleging that -any patent claim is infringed by making, using, selling, offering for -sale, or importing the Program or any portion of it. - - 11. Patents. - - A "contributor" is a copyright holder who authorizes use under this -License of the Program or a work on which the Program is based. The -work thus licensed is called the contributor's "contributor version". - - A contributor's "essential patent claims" are all patent claims -owned or controlled by the contributor, whether already acquired or -hereafter acquired, that would be infringed by some manner, permitted -by this License, of making, using, or selling its contributor version, -but do not include claims that would be infringed only as a -consequence of further modification of the contributor version. For -purposes of this definition, "control" includes the right to grant -patent sublicenses in a manner consistent with the requirements of -this License. - - Each contributor grants you a non-exclusive, worldwide, royalty-free -patent license under the contributor's essential patent claims, to -make, use, sell, offer for sale, import and otherwise run, modify and -propagate the contents of its contributor version. - - In the following three paragraphs, a "patent license" is any express -agreement or commitment, however denominated, not to enforce a patent -(such as an express permission to practice a patent or covenant not to -sue for patent infringement). To "grant" such a patent license to a -party means to make such an agreement or commitment not to enforce a -patent against the party. - - If you convey a covered work, knowingly relying on a patent license, -and the Corresponding Source of the work is not available for anyone -to copy, free of charge and under the terms of this License, through a -publicly available network server or other readily accessible means, -then you must either (1) cause the Corresponding Source to be so -available, or (2) arrange to deprive yourself of the benefit of the -patent license for this particular work, or (3) arrange, in a manner -consistent with the requirements of this License, to extend the patent -license to downstream recipients. "Knowingly relying" means you have -actual knowledge that, but for the patent license, your conveying the -covered work in a country, or your recipient's use of the covered work -in a country, would infringe one or more identifiable patents in that -country that you have reason to believe are valid. - - If, pursuant to or in connection with a single transaction or -arrangement, you convey, or propagate by procuring conveyance of, a -covered work, and grant a patent license to some of the parties -receiving the covered work authorizing them to use, propagate, modify -or convey a specific copy of the covered work, then the patent license -you grant is automatically extended to all recipients of the covered -work and works based on it. - - A patent license is "discriminatory" if it does not include within -the scope of its coverage, prohibits the exercise of, or is -conditioned on the non-exercise of one or more of the rights that are -specifically granted under this License. You may not convey a covered -work if you are a party to an arrangement with a third party that is -in the business of distributing software, under which you make payment -to the third party based on the extent of your activity of conveying -the work, and under which the third party grants, to any of the -parties who would receive the covered work from you, a discriminatory -patent license (a) in connection with copies of the covered work -conveyed by you (or copies made from those copies), or (b) primarily -for and in connection with specific products or compilations that -contain the covered work, unless you entered into that arrangement, -or that patent license was granted, prior to 28 March 2007. - - Nothing in this License shall be construed as excluding or limiting -any implied license or other defenses to infringement that may -otherwise be available to you under applicable patent law. - - 12. No Surrender of Others' Freedom. - - If conditions are imposed on you (whether by court order, agreement or -otherwise) that contradict the conditions of this License, they do not -excuse you from the conditions of this License. If you cannot convey a -covered work so as to satisfy simultaneously your obligations under this -License and any other pertinent obligations, then as a consequence you may -not convey it at all. For example, if you agree to terms that obligate you -to collect a royalty for further conveying from those to whom you convey -the Program, the only way you could satisfy both those terms and this -License would be to refrain entirely from conveying the Program. - - 13. Remote Network Interaction; Use with the GNU General Public License. - - Notwithstanding any other provision of this License, if you modify the -Program, your modified version must prominently offer all users -interacting with it remotely through a computer network (if your version -supports such interaction) an opportunity to receive the Corresponding -Source of your version by providing access to the Corresponding Source -from a network server at no charge, through some standard or customary -means of facilitating copying of software. This Corresponding Source -shall include the Corresponding Source for any work covered by version 3 -of the GNU General Public License that is incorporated pursuant to the -following paragraph. - - Notwithstanding any other provision of this License, you have -permission to link or combine any covered work with a work licensed -under version 3 of the GNU General Public License into a single -combined work, and to convey the resulting work. The terms of this -License will continue to apply to the part which is the covered work, -but the work with which it is combined will remain governed by version -3 of the GNU General Public License. - - 14. Revised Versions of this License. - - The Free Software Foundation may publish revised and/or new versions of -the GNU Affero General Public License from time to time. Such new versions -will be similar in spirit to the present version, but may differ in detail to -address new problems or concerns. - - Each version is given a distinguishing version number. If the -Program specifies that a certain numbered version of the GNU Affero General -Public License "or any later version" applies to it, you have the -option of following the terms and conditions either of that numbered -version or of any later version published by the Free Software -Foundation. If the Program does not specify a version number of the -GNU Affero General Public License, you may choose any version ever published -by the Free Software Foundation. - - If the Program specifies that a proxy can decide which future -versions of the GNU Affero General Public License can be used, that proxy's -public statement of acceptance of a version permanently authorizes you -to choose that version for the Program. - - Later license versions may give you additional or different -permissions. However, no additional obligations are imposed on any -author or copyright holder as a result of your choosing to follow a -later version. - - 15. Disclaimer of Warranty. - - THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY -APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT -HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY -OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, -THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR -PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM -IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF -ALL NECESSARY SERVICING, REPAIR OR CORRECTION. - - 16. Limitation of Liability. - - IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING -WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS -THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY -GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE -USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF -DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD -PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), -EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF -SUCH DAMAGES. - - 17. Interpretation of Sections 15 and 16. - - If the disclaimer of warranty and limitation of liability provided -above cannot be given local legal effect according to their terms, -reviewing courts shall apply local law that most closely approximates -an absolute waiver of all civil liability in connection with the -Program, unless a warranty or assumption of liability accompanies a -copy of the Program in return for a fee. - - END OF TERMS AND CONDITIONS - - How to Apply These Terms to Your New Programs - - If you develop a new program, and you want it to be of the greatest -possible use to the public, the best way to achieve this is to make it -free software which everyone can redistribute and change under these terms. - - To do so, attach the following notices to the program. It is safest -to attach them to the start of each source file to most effectively -state the exclusion of warranty; and each file should have at least -the "copyright" line and a pointer to where the full notice is found. - - - Copyright (C) - - This program is free software: you can redistribute it and/or modify - it under the terms of the GNU Affero General Public License as published by - the Free Software Foundation, either version 3 of the License, or - (at your option) any later version. - - This program is distributed in the hope that it will be useful, - but WITHOUT ANY WARRANTY; without even the implied warranty of - MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the - GNU Affero General Public License for more details. - - You should have received a copy of the GNU Affero General Public License - along with this program. If not, see . - -Also add information on how to contact you by electronic and paper mail. - - If your software can interact with users remotely through a computer -network, you should also make sure that it provides a way for users to -get its source. For example, if your program is a web application, its -interface could display a "Source" link that leads users to an archive -of the code. There are many ways you could offer source, and different -solutions will be better for different programs; see section 13 for the -specific requirements. - - You should also get your employer (if you work as a programmer) or school, -if any, to sign a "copyright disclaimer" for the program, if necessary. -For more information on this, and how to apply and follow the GNU AGPL, see -. +MIT License + +Copyright (c) 2026 Marko Vejnovic + +Permission is hereby granted, free of charge, to any person obtaining a copy +of this software and associated documentation files (the "Software"), to deal +in the Software without restriction, including without limitation the rights +to use, copy, modify, merge, publish, distribute, sublicense, and/or sell +copies of the Software, and to permit persons to whom the Software is +furnished to do so, subject to the following conditions: + +The above copyright notice and this permission notice shall be included in all +copies or substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR +IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE +AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER +LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, +OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE +SOFTWARE. diff --git a/NOTICE b/NOTICE deleted file mode 100644 index ed0d264f..00000000 --- a/NOTICE +++ /dev/null @@ -1,26 +0,0 @@ -Hyper -Copyright (C) 2026 Marko Vejnovic - -This program is free software: you can redistribute it and/or modify it -under the terms of the GNU Affero General Public License as published by -the Free Software Foundation, either version 3 of the License, or (at your -option) any later version (AGPL-3.0-or-later). - -This program is distributed in the hope that it will be useful, but WITHOUT -ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS -FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more -details. The full license text is in the LICENSE file at the root of this -repository, and also available at . - ----------------------------------------------------------------------------- - -CONTRIBUTOR LICENSE - -All contributions to this project are governed by the Contributor License -Agreement in CLA.md. By submitting a contribution (a patch, pull request, or -any other form), you keep the copyright to your contribution and grant Marko -Vejnovic a perpetual, worldwide, non-exclusive, sublicensable license to use it -and to relicense or dual-license it as part of the project. This lets the -project be relicensed and dual-licensed by a single party without asking -contributors to give up ownership of their work. See CLA.md for -the full terms. diff --git a/README.md b/README.md index 9494514c..f74f9d92 100644 --- a/README.md +++ b/README.md @@ -5,7 +5,7 @@

Hex.pm version Hexdocs - License: AGPL-3.0 + License: MIT Last commit Coverage Discord @@ -126,35 +126,13 @@ Contributions are welcome. Hyper is a technical-first project with a strict quality gate (`mix check` must pass) and a few Linux/Firecracker prerequisites. Read [CONTRIBUTING.md](CONTRIBUTING.md) before opening a pull request. -Note that all contributions are governed by the -[Contributor License Agreement](CLA.md): by submitting a PR you keep the -copyright to your contribution and grant the project owner a broad, -non-exclusive license (including the right to relicense and dual-license -Hyper). You are not asked to give up ownership. If that is a dealbreaker for -you, it is better to know up front. +Contributions are accepted under the project's license (MIT): by opening a +pull request you agree that your contribution is licensed under the same terms, +and you retain the copyright to your own work. No separate contributor +agreement is required. ## License -Hyper is licensed under the GNU Affero General Public License v3.0 or later -(AGPL-3.0-or-later). See [LICENSE](LICENSE) and [NOTICE](NOTICE). Contributions -are governed by the [Contributor License Agreement](CLA.md). - -### Why AGPL? - -Hyper is infrastructure meant to be run as a service. If you modify Hyper and -offer it to others over a network, we expect you to share your changes -publicly. The product is built by humans for humans and we want to keep it that -way -- we don't want anyone taking Hyper closed-source and reselling it. Hyper -is free of charge, and we expect you to play nicely with that philosophy. In -practical terms, for most users: - -- **Running Hyper as-is internally** imposes no copyleft obligations. You do - not need to share your source. -- **The VMs and workloads Hyper runs are yours.** Copyleft covers Hyper itself, - not the things you orchestrate with it. Your code stays your code. -- **Modifying Hyper** and offering any form of product built with it as a - service, however, **requires** that you make your modifications open-source. - We wish to make Hyper better, and that means you need to be a part of it. - -This section is a plain-language summary, not legally binding. For the -authoritative terms, see [LICENSE](LICENSE). +Hyper is licensed under the MIT License. See [LICENSE](LICENSE). Contributions +are accepted under the same license (inbound=outbound); contributors retain +copyright to their work. diff --git a/mix.exs b/mix.exs index 0dd99dff..e0ba9b76 100644 --- a/mix.exs +++ b/mix.exs @@ -187,7 +187,7 @@ defmodule Hyper.MixProject do # The OTP app is `:hyper`, but `hyper` is already taken on Hex, so the # package publishes as `hypervm`. Package name and app name are independent. name: "hypervm", - licenses: ["AGPL-3.0-or-later"], + licenses: ["MIT"], # priv/firecracker ships the OpenAPI spec so the `:firecracker_gen` compiler # can regenerate the bindings in a consumer's build (they are gitignored, so # not in `lib`). @@ -204,7 +204,7 @@ defmodule Hyper.MixProject do # load even for plain `cargo build`. files: ~w( lib priv/firecracker priv/repo priv/vmlinux proto config mix.exs - README.md LICENSE NOTICE CLA.md + README.md LICENSE native/guest-agent/src native/guest-agent/tests native/guest-agent/build.rs native/guest-agent/Cargo.toml native/guest-agent/Cargo.lock native/guest-agent/.cargo diff --git a/native/suidhelper/Cargo.toml b/native/suidhelper/Cargo.toml index 5d272603..51748e3b 100644 --- a/native/suidhelper/Cargo.toml +++ b/native/suidhelper/Cargo.toml @@ -9,7 +9,7 @@ name = "hyper-suidhelper" version = "0.1.0" edition = "2021" description = "Tiny setuid-root helper that runs a whitelisted set of device commands for the unprivileged Hyper node." -license = "AGPL-3.0-or-later" +license = "MIT" repository = "https://github.com/harmont-dev/hyper" [features] diff --git a/native/suidhelper/build.rs b/native/suidhelper/build.rs index c3de1f5d..de04496b 100644 --- a/native/suidhelper/build.rs +++ b/native/suidhelper/build.rs @@ -1,4 +1,4 @@ -// SPDX-License-Identifier: AGPL-3.0-only +// SPDX-License-Identifier: MIT //! Build guard: keep the `insecure_test_seams` feature out of any release //! artifact. Tests build in the `debug` profile, so they are unaffected. diff --git a/native/suidhelper/meta/Cargo.toml b/native/suidhelper/meta/Cargo.toml index 417e5f41..fc180436 100644 --- a/native/suidhelper/meta/Cargo.toml +++ b/native/suidhelper/meta/Cargo.toml @@ -2,7 +2,7 @@ name = "hyper-suidhelper-meta" version = "0.1.0" edition = "2021" -license = "AGPL-3.0-or-later" +license = "MIT" description = "Shared constants for the hyper-suidhelper checksum section (binary + xtask)." [dependencies] diff --git a/native/suidhelper/src/config.rs b/native/suidhelper/src/config.rs index 09e43c5c..39dd1762 100644 --- a/native/suidhelper/src/config.rs +++ b/native/suidhelper/src/config.rs @@ -1,4 +1,4 @@ -// SPDX-License-Identifier: AGPL-3.0-only +// SPDX-License-Identifier: MIT //! Runtime host configuration, read from a single root-owned TOML file. //! //! ## UID/GID range divergence diff --git a/native/suidhelper/src/security_gate.rs b/native/suidhelper/src/security_gate.rs index d82caea3..4b361856 100644 --- a/native/suidhelper/src/security_gate.rs +++ b/native/suidhelper/src/security_gate.rs @@ -1,4 +1,4 @@ -// SPDX-License-Identifier: AGPL-3.0-only +// SPDX-License-Identifier: MIT //! Central security gate: the single place that decides whether this process is //! running in INSECURE TEST MODE, resolved once at startup. //! diff --git a/native/suidhelper/src/tools/chroot_jail/grant.rs b/native/suidhelper/src/tools/chroot_jail/grant.rs index c0c9aab2..d6ccadd8 100644 --- a/native/suidhelper/src/tools/chroot_jail/grant.rs +++ b/native/suidhelper/src/tools/chroot_jail/grant.rs @@ -1,4 +1,4 @@ -// SPDX-License-Identifier: AGPL-3.0-only +// SPDX-License-Identifier: MIT //! Shared grant-socket logic reused by `grant-api` and `grant-vsock`. //! //! Both ops chown a jail-confined Unix-domain socket to the helper's caller and diff --git a/native/suidhelper/src/tools/chroot_jail/grant_api.rs b/native/suidhelper/src/tools/chroot_jail/grant_api.rs index a554ca8c..8063db77 100644 --- a/native/suidhelper/src/tools/chroot_jail/grant_api.rs +++ b/native/suidhelper/src/tools/chroot_jail/grant_api.rs @@ -1,4 +1,4 @@ -// SPDX-License-Identifier: AGPL-3.0-only +// SPDX-License-Identifier: MIT //! `chroot-jail grant-api`: hand the firecracker API socket to the node user so //! the unprivileged controller can `connect()` to it. //! diff --git a/native/suidhelper/src/tools/chroot_jail/grant_vsock.rs b/native/suidhelper/src/tools/chroot_jail/grant_vsock.rs index 09cf4a1f..b702af8d 100644 --- a/native/suidhelper/src/tools/chroot_jail/grant_vsock.rs +++ b/native/suidhelper/src/tools/chroot_jail/grant_vsock.rs @@ -1,4 +1,4 @@ -// SPDX-License-Identifier: AGPL-3.0-only +// SPDX-License-Identifier: MIT //! `chroot-jail grant-vsock`: hand the firecracker vsock Unix-domain socket to //! the node user so the unprivileged controller can connect the guest via AF_VSOCK. //! diff --git a/native/suidhelper/src/tools/chroot_jail/mod.rs b/native/suidhelper/src/tools/chroot_jail/mod.rs index 40fbbfb9..a53665d7 100644 --- a/native/suidhelper/src/tools/chroot_jail/mod.rs +++ b/native/suidhelper/src/tools/chroot_jail/mod.rs @@ -1,4 +1,4 @@ -// SPDX-License-Identifier: AGPL-3.0-only +// SPDX-License-Identifier: MIT //! `chroot-jail`: per-VM chroot/jail lifecycle. mod grant; diff --git a/native/suidhelper/src/tools/chroot_jail/prepare.rs b/native/suidhelper/src/tools/chroot_jail/prepare.rs index b229f6bd..ba4e03dd 100644 --- a/native/suidhelper/src/tools/chroot_jail/prepare.rs +++ b/native/suidhelper/src/tools/chroot_jail/prepare.rs @@ -1,4 +1,4 @@ -// SPDX-License-Identifier: AGPL-3.0-only +// SPDX-License-Identifier: MIT //! `chroot-jail prepare`: stage the kernel file and create the rootfs device node //! inside a VM chroot, via the [`ChrootJail`] builder. diff --git a/native/suidhelper/src/tools/chroot_jail/remove.rs b/native/suidhelper/src/tools/chroot_jail/remove.rs index 7574b364..9d16d474 100644 --- a/native/suidhelper/src/tools/chroot_jail/remove.rs +++ b/native/suidhelper/src/tools/chroot_jail/remove.rs @@ -1,4 +1,4 @@ -// SPDX-License-Identifier: AGPL-3.0-only +// SPDX-License-Identifier: MIT //! `chroot-jail remove`: delete a VM's stale chroot and cgroup leaf before //! relaunching the jailer. //! diff --git a/native/suidhelper/src/tools/jailer.rs b/native/suidhelper/src/tools/jailer.rs index 78c12b78..db3fcedc 100644 --- a/native/suidhelper/src/tools/jailer.rs +++ b/native/suidhelper/src/tools/jailer.rs @@ -1,4 +1,4 @@ -// SPDX-License-Identifier: AGPL-3.0-only +// SPDX-License-Identifier: MIT //! The `jailer` subcommand: validate the BEAM's arguments, re-acquire root //! permanently, and `execve` the firecracker jailer in our place. //! diff --git a/native/suidhelper/src/tools/network/mod.rs b/native/suidhelper/src/tools/network/mod.rs index ca2a9007..e1cb94e6 100644 --- a/native/suidhelper/src/tools/network/mod.rs +++ b/native/suidhelper/src/tools/network/mod.rs @@ -1,4 +1,4 @@ -// SPDX-License-Identifier: AGPL-3.0-only +// SPDX-License-Identifier: MIT //! `network`: per-VM egress networking (netns + veth + TAP + NAT). //! //! Each op ([`prepare`], [`teardown`], [`host_init`]) derives its `ip`/`nft` diff --git a/native/suidhelper/src/util/chroot_jail.rs b/native/suidhelper/src/util/chroot_jail.rs index 22c6523a..d72e6396 100644 --- a/native/suidhelper/src/util/chroot_jail.rs +++ b/native/suidhelper/src/util/chroot_jail.rs @@ -1,4 +1,4 @@ -// SPDX-License-Identifier: AGPL-3.0-only +// SPDX-License-Identifier: MIT //! Declarative builder for a VM's chroot jail contents. use crate::config::Config; diff --git a/native/suidhelper/src/util/jailer.rs b/native/suidhelper/src/util/jailer.rs index 3743f451..74ddc20c 100644 --- a/native/suidhelper/src/util/jailer.rs +++ b/native/suidhelper/src/util/jailer.rs @@ -1,4 +1,4 @@ -// SPDX-License-Identifier: AGPL-3.0-only +// SPDX-License-Identifier: MIT //! Typed invocation of the firecracker jailer: the validated argument newtypes //! and the `execve` mechanics behind the `jailer` subcommand. //! diff --git a/native/suidhelper/src/util/path.rs b/native/suidhelper/src/util/path.rs index 2422f287..91393136 100644 --- a/native/suidhelper/src/util/path.rs +++ b/native/suidhelper/src/util/path.rs @@ -1,4 +1,4 @@ -// SPDX-License-Identifier: AGPL-3.0-only +// SPDX-License-Identifier: MIT //! Fallible conversion of paths and strings to NUL-terminated C strings, for //! handing to `execve`-family syscalls. //! diff --git a/native/suidhelper/src/util/safe_dev.rs b/native/suidhelper/src/util/safe_dev.rs index 3c780a61..cc335483 100644 --- a/native/suidhelper/src/util/safe_dev.rs +++ b/native/suidhelper/src/util/safe_dev.rs @@ -1,4 +1,4 @@ -// SPDX-License-Identifier: AGPL-3.0-only +// SPDX-License-Identifier: MIT //! Validated device-name operands. //! //! The privileged tools must only ever touch Hyper's own devices, never diff --git a/native/suidhelper/src/util/safe_dir.rs b/native/suidhelper/src/util/safe_dir.rs index ccf886d9..515b1e81 100644 --- a/native/suidhelper/src/util/safe_dir.rs +++ b/native/suidhelper/src/util/safe_dir.rs @@ -1,4 +1,4 @@ -// SPDX-License-Identifier: AGPL-3.0-only +// SPDX-License-Identifier: MIT //! Directory handles with fd-relative operations. //! //! A [`SafeDir`] owns a directory fd (closed on drop). It is two things at once: diff --git a/native/suidhelper/src/util/safe_file.rs b/native/suidhelper/src/util/safe_file.rs index 22744f7a..50b6bf56 100644 --- a/native/suidhelper/src/util/safe_file.rs +++ b/native/suidhelper/src/util/safe_file.rs @@ -1,4 +1,4 @@ -// SPDX-License-Identifier: AGPL-3.0-only +// SPDX-License-Identifier: MIT //! Typestate-validated file descriptors. //! //! Each type parameter is an independent axis (file type, ownership, mode); the diff --git a/native/suidhelper/src/util/safe_path.rs b/native/suidhelper/src/util/safe_path.rs index 92b90673..6e9955e8 100644 --- a/native/suidhelper/src/util/safe_path.rs +++ b/native/suidhelper/src/util/safe_path.rs @@ -1,4 +1,4 @@ -// SPDX-License-Identifier: AGPL-3.0-only +// SPDX-License-Identifier: MIT //! Typestate-validated filesystem *names*. use std::marker::PhantomData; From 38fabf6b7a07c044936fa0c2f5730315661f3f1d Mon Sep 17 00:00:00 2001 From: Marko Vejnovic Date: Thu, 9 Jul 2026 04:22:38 +0000 Subject: [PATCH 8/8] chore: hold copyright as Harmont, Inc. --- LICENSE | 2 +- README.md | 3 +-- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/LICENSE b/LICENSE index d3f90b36..80d9826f 100644 --- a/LICENSE +++ b/LICENSE @@ -1,6 +1,6 @@ MIT License -Copyright (c) 2026 Marko Vejnovic +Copyright (c) 2026 Harmont, Inc. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal diff --git a/README.md b/README.md index f74f9d92..8b34ea01 100644 --- a/README.md +++ b/README.md @@ -134,5 +134,4 @@ agreement is required. ## License Hyper is licensed under the MIT License. See [LICENSE](LICENSE). Contributions -are accepted under the same license (inbound=outbound); contributors retain -copyright to their work. +are accepted under the same license.