User Story
As a maintainer,
I want the LICENSE badge in README.md to reflect the project’s actual AGPLv3 license
so that contributors and users avoid compliance risks and confusion.
Background
The repository’s LICENSE file contains the GNU AGPLv3 license, but the README.md displays an MIT license badge. This mismatch creates ambiguity about legal obligations, particularly for downstream users or contributors who might assume MIT terms apply. The inconsistency occurs in:
README.md: Line 2 shows [](https://opensource.org/licenses/MIT)
LICENSE: Full AGPLv3 text confirms the correct license.
This discrepancy could lead to unintentional violations of AGPLv3 requirements, such as failing to disclose modified source code when deploying networked services.
Acceptance Criteria
User Story
As a maintainer,
I want the LICENSE badge in README.md to reflect the project’s actual AGPLv3 license
so that contributors and users avoid compliance risks and confusion.
Background
The repository’s LICENSE file contains the GNU AGPLv3 license, but the README.md displays an MIT license badge. This mismatch creates ambiguity about legal obligations, particularly for downstream users or contributors who might assume MIT terms apply. The inconsistency occurs in:
README.md: Line 2 shows[](https://opensource.org/licenses/MIT)LICENSE: Full AGPLv3 text confirms the correct license.This discrepancy could lead to unintentional violations of AGPLv3 requirements, such as failing to disclose modified source code when deploying networked services.
Acceptance Criteria
README.mdto replace the MIT badge with the AGPLv3 badge using the markdown:[](https://www.gnu.org/licenses/agpl-3.0)setup.pycorrectly specifies AGPLv3).