Skip to content

docs: relicense from GPL-3.0 to AGPL-3.0 - #8

Merged
pjhartlieb merged 1 commit into
blacklanternsecurity:mainfrom
singlerider:license-agpl
Oct 20, 2026
Merged

pjhartlieb merged 1 commit into
blacklanternsecurity:mainfrom
singlerider:license-agpl

Conversation

@singlerider

Copy link
Copy Markdown
Contributor

What

LICENSE moves from GPL-3.0 to AGPL-3.0. package.json moves with it, in the same commit.

Why

Every Black Lantern original carries AGPL-3.0. This repository is an original,
not a fork, so this is the copyright holder relicensing its own work. The
notices carry either version 3 of the License, or (at your option) any later version, and GPLv3 section 13 already permits AGPLv3 interoperation, so making
the AGPL grant explicit needs no contributor sign-off.

Manifest

A tree that ships an AGPL-3.0 file next to a manifest naming something else is
self-contradictory at the point a packager reads it, so both edits belong in
one commit rather than a follow-up.

Validation

  • LICENSE first line reads GNU AFFERO GENERAL PUBLIC LICENSE
  • JSON manifests parse under json.load
  • Only the license file and its manifests are touched; no code change

Refs #151

`agentsee` is a Black Lantern original, so this is the copyright holder
relicensing its own work. The notices carry `either version 3 of the
License, or (at your option) any later version`, and GPLv3 section 13
already permits AGPLv3 interoperation, so making the AGPL grant explicit
needs no contributor sign-off.

The file is the same AGPL-3.0 text `bbot` carries.

The manifest moves in the same commit. A tree that ships an AGPL-3.0 file
next to a manifest naming something else is self-contradictory at the point
a packager reads it: `package.json`.

Refs #151
@pjhartlieb
pjhartlieb merged commit cb1ce80 into blacklanternsecurity:main Oct 20, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants