Blog··7 min read

Why DarkMoon Community Is Moving from GPLv3 to AGPLv3

DarkMoon Community's master branch is now AGPL-3.0; releases up to v1.6.0 stay GPL-3.0 and the CLA is under legal review. The reason and the exact status.

DarkMoon research series·D. Open source & licence·Article 18 of 23·All 23 articles

This article explains a decision and its current state. It is not legal advice. The LICENSE text is what applies, and the reference page, LICENSING.md, is itself still a draft under review by counsel.

Introduction

DarkMoon Community, the open-source edition of DarkMoon published at ASCIT31/Dark-Moon, is moving from the GNU General Public License v3.0 (GPL-3.0) to the GNU Affero General Public License v3.0 (AGPL-3.0-only). The title of this article says « is moving » on purpose: the licence file has changed on the main branch, but the process around it (final licensing page, contributor agreement, first release under the new licence) is not finished. This article states what has happened, what has not, and why.

Problem

The GPL was designed for software that people install. Its obligations start when someone distributes a copy: whoever passes on the program, modified or not, must pass on the source under the same licence.

DarkMoon is increasingly operated as a service: a pentest platform one team runs for others, through a portal, an API or a chat interface. Under the GPL, a company could modify DarkMoon, offer the modified version as a hosted service, and never share its changes, because it never handed anyone a copy. This is the gap the AGPL was written to close.

Methodology

What the AGPL adds

The GPL-3.0 and the AGPL-3.0 are almost identical. The substantive difference is section 13 of the AGPL, « Remote Network Interaction »: if you modify the program and let users interact with your modified version remotely over a network, you must offer those users the corresponding source of your version.

SituationGPL-3.0AGPL-3.0
Run DarkMoon for yourself or inside your organisation, modified or notno obligationno obligation
Give or sell a copy to someone elseprovide source under GPL-3.0provide source under AGPL-3.0
Let others interact over a network with a modified DarkMoonno source obligationoffer those users the source of your modified version

The goal is reciprocity: improvements made to DarkMoon come back to its users even when DarkMoon is consumed as a service. The AGPL does not restrict who may use the software or for what purpose; LICENSING.md says this explicitly.

How the change was made

The change follows a few rules, all visible in the public repository:

  • Nothing is withdrawn. A licence change cannot take back rights already granted. Every version published up to commit edfe9cb (27 October 2026) stays under the GPL-3.0. That includes every release up to v1.6.0 (25 October 2026).
  • Outside contributions are not relicensed. Contributions made by people outside ASC before the switch stay under the GPL-3.0. They are listed by name, pull request and file in LICENSING.md, and remain in the repository combined with the AGPL code, as section 13 of the GPL-3.0 and section 13 of the AGPL-3.0 both allow. Contributors who want their contribution under the AGPL as well, or removed, can open an issue.
  • History is kept, not rewritten. The repository holds LICENSE (AGPL-3.0), LICENSES/AGPL-3.0.txt and LICENSES/GPL-3.0.txt, and the README carries a « License change » banner.
Diagram. Figure 1. Licence timeline. Dates from the repository and its release list.
Figure 1. Licence timeline. Dates from the repository and its release list.

Real results: the state on 20 November 2026

ItemStateWhere to check
LICENSE on masterGNU AGPL v3.0 since 19 November 2026; GitHub reports AGPL-3.0 for the repositoryLICENSE
Change setPR #59, « Community: attack paths, Terminal Explorer, hardening, AGPL-3.0 (draft, legal review pending) », merged 19 November 2026PR page
Releases ≤ v1.6.0GPL-3.0, unchangedreleases
Earlier outside contributionsGPL-3.0, listed in LICENSING.mdLICENSING.md
LICENSING.mdpublished, marked « Draft under legal review »same
CLA (individual) and Corporate CLAdrafts under legal review; cannot be signed yetCLA.md
First AGPL releasenot tagged yet; the latest release is still v1.6.0 (GPL-3.0)release list
New contributionsaccepted under AGPL-3.0LICENSING.md

The same PR #59 brought the attack-path engine port and the Terminal Explorer to Community. Those components, documented in our research repositories, are therefore among the first code published on master under the AGPL.

What this means for you today

  • You run DarkMoon on your own systems or for your own assessments: nothing changes. Running it is free under both licences.
  • You use v1.6.0 or earlier: that code is GPL-3.0 and stays GPL-3.0.
  • You build on current master: that code is AGPL-3.0. If you distribute it, or let others interact over a network with a modified version, section 13 applies.
  • You want to contribute: your contribution is accepted under the AGPL-3.0. The CLA, once reviewed, will additionally be required; it is not in force today.

Limits

  • The legal process is not complete. LICENSING.md, the CLA and the Corporate CLA are drafts under review by counsel; their wording may change before the first AGPL release.
  • No AGPL release exists yet. Until one is tagged, the only released versions are GPL-3.0.
  • This is not legal advice. Whether a specific deployment counts as « remote network interaction » depends on facts; ask your own counsel.
  • The research repositories cited below are not legal authority. Both are themselves published under the AGPL-3.0 following the Dark-Moon set-up, but they document technology, not licensing law.
  • Trademarks are separate. The licences cover the code, not the DarkMoon name and logos.

Figures

  • Figure 1 (Mermaid timeline): licence history.
DarkMoon Terminal Explorer in the open-source Community edition, Workspace tab, on lab campaigns against intentionally vulnerable training apps: totals (188 findings, 115 exploited, 36 critical, 24 attack paths, 0 evidence-backed), recent campaigns and projects, an executive panel with a rated Cyber Score of E 0/100 and the first treatment actions, and a severity breakdown of the selected campaign.
Figure 2. The Terminal Explorer in DarkMoon Community, one of the components PR #59 brought to master under the AGPL: a local, read-only workspace with findings, campaigns and an executive Cyber Score panel. Lab data from intentionally vulnerable training apps.Captured 20 November 2026 from the Terminal Explorer (current interface).

Sources (verified)

All pages fetched on 2026-11-20.

Research, source code & reproducibility

Related reading: AGPLv3, Open Source and Commercial Editions: Understanding the Tradeoffs · Building DarkMoon in the Open: Research, Benchmarks, Failures and Reproducibility · Bringing DarkMoon to the Terminal: Building an OpenCode Explorer


Questions about the change can be asked in an issue on ASCIT31/Dark-Moon. If you contributed before the switch and want your contribution handled differently, that is the place too.

Next
Run it against your own lab

Darkmoon is open source (AGPL-3.0) and self hosted. Clone it, point it at a target you own, and read every line.