Add AGPL-3.0 license

[Copilot]

Adds licensing metadata to the repository so GitHub recognizes it as AGPL-3.0 licensed.

Changes

• LICENSE — New file at repo root (needs the full AGPL-3.0 text pasted in; file is currently a placeholder due to network restrictions in the authoring environment)
• README.md — Added ## License section linking to the LICENSE file
• package.json — Added "license": "AGPL-3.0-only" top-level field

⚠️ Action required

The LICENSE file is empty and must be populated with the official AGPL-3.0 text from https://www.gnu.org/licenses/agpl-3.0.txt before merging. GitHub's license detection depends on this file having the correct content.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• www.gnu.org
  • Triggering command: /usr/bin/curl curl -s REDACTED -o /tmp/agpl-3.0.txt (dns block)
  • Triggering command: /usr/bin/python3 python3 -c import urllib.request try: url = 'REDACTED' with urllib.request.urlopen(url, timeout=10) as r: print(r.read().decode()) except Exception as e: print('Error:', e) (dns block)
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

Add the GNU Affero General Public License v3.0 (AGPL-3.0) to the repository.

Requirements:

1. Add a root-level LICENSE file containing the official, unmodified text of the GNU Affero General Public License version 3 (AGPL-3.0).
2. Update the project documentation to clearly state the license:
   • Add or update a "License" section in README.md (or the primary README) that says the project is licensed under AGPL-3.0 and references the LICENSE file.
3. If the repository contains common package metadata files, update license metadata where appropriate (do this only when it’s clearly applicable):
   • package.json -> set license to AGPL-3.0-only (or AGPL-3.0-or-later if the project indicates that preference).
   • pyproject.toml / setup.cfg / setup.py -> update license fields/classifiers accordingly.
   • Other ecosystem manifests as relevant.
     Ensure changes are consistent and do not break existing tooling.
4. Keep changes minimal: no refactors unrelated to licensing.

Acceptance criteria:

• GitHub recognizes the repository as AGPL-3.0 licensed (via the LICENSE file).
• README clearly points to the license.
• Any updated package metadata passes existing formatting/linting conventions.

Create a pull request with these changes.

The following is the prior conversation context from the user's chat exploration (may be truncated):

User: how do i add agpl license to this project

Assistant: Add an AGPL-3.0 license by (1) committing a LICENSE file with the official text, and (2) updating your README (and optionally file headers / package.json) to clearly state the license.

1) Add the LICENSE file

1. In your repo merill/graphxray, create a new file at the repo root named LICENSE (or LICENSE.txt).
2. Paste the GNU Affero General Public License v3.0 full text (the standard license text).
3. Commit it to your default branch.

GitHub UI path: Add file → Create new file → LICENSE.

2) Update README to declare the license (recommended)

Add a section like:

## License
Licensed under the GNU Affero General Public License v3.0 (AGPL-3.0). See the LICENSE file.

3) (Optional but common) Add AGPL notice headers to source files

AGPL doesn’t require per-file headers if you ship the LICENSE, but many projects add a short header to key source files to make it unambiguous.

4) (Optional) If you have a package manifest, set the license field

• npm/package.json: "license": "AGPL-3.0-only" (or AGPL-3.0-or-later)
• Python pyproject.toml: include the appropriate license metadata
• etc.

Important AGPL-specific reminder

If you run this software as a network service and users interact with it over a network, AGPL requires you to offer the corresponding source code to those users (including your modifications).

If you tell me what stack this repo uses (Node/Python/Go/etc.) and whether it’s a library or a web service, I can suggest the best places to add the license metadata and notices.

User: add agpl license to this repo

Assistant: I’m waiting for you to accept or reject the GitHub tool action (so I can apply the AGPL license changes and open the PR).

This pull request was created from Copilot chat.