LEXCEPTIO quietly flags its fork as AGPL

A one-line licensing change that downstream forks need to read before they pull anything from LEXCEPTIO.

compliance

The change itself is tiny: LEXCEPTIO's project manifests now declare the fork as AGPL-3.0-only. The legal weight is not tiny. AGPL is a "network copyleft" license - its defining clause says that if you run AGPL-covered code as a hosted service, you have to publish your source, even if you never distribute the software the old-fashioned way. For most software licenses, simply running the code on your own servers triggers no obligations. AGPL is the exception.

The practical takeaway is for anyone building on top of this fork. If your own product sits under a more permissive license and you pull work from LEXCEPTIO after this point, you may be importing publish-your-source obligations you didn't sign up for. It's worth a legal sign-off before merging, not after. One wrinkle: the change is labelled as a routine dependency update, which buries a licensing decision under a misleading title - exactly the kind of thing that makes a later audit harder.

So what Anyone building a commercial or closed product on top of this fork should get licensing sign-off before pulling further changes from LEXCEPTIO.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

1 commit from LEXCEPTIO/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
61deeb01 update dependencies LEXCEPTIO 2026-05-10 ↗ GitHub

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-225.md from inside the repo you want the changes in.

⬇ Download capture-thread-225.md