Add AGPL-3.0 license metadata and update Code of Conduct to v2.1

[Copilot]

Complete open source licensing documentation for AGPL-3.0 release.

Changes

• package.json: Added "license": "AGPL-3.0" field for npm package metadata
• CODE_OF_CONDUCT.md: Updated Contributor Covenant reference from v2.0 to v2.1 and changed enforcement contact to opensource@bitsleuth.ai

Already Compliant

The following were already properly configured and required no changes:

• README.md (license badge, contributing section, support section)
• CONTRIBUTING.md (community guidelines, PR process)
• SECURITY.md (vulnerability reporting, supported versions)
• LICENSE (full AGPL-3.0 text)

Original prompt

I am making the repo Wallet open source under the GNU Affero General Public License v3.0.

Can you make sure the BitSleuth Wallet project has all the relevant documentation for a open-source project.

Update README.md to reflect AGPL-3.0 license and open source nature

• Update license badge from "Proprietary" to "AGPL-3.0"
• Update contributing section to welcome community contributions
• Update license section to reflect AGPL-3.0 and open source status
• Update support section for public repository

Update CONTRIBUTING.md for open source contributions

• Remove proprietary language
• Add community contribution guidelines
• Add pull request process
• Keep existing documentation organization guidelines

Update CODE_OF_CONDUCT.md using Contributor Covenant

• Use standard Contributor Covenant v2.1
• Customize contact information

Update SECURITY.md with vulnerability reporting guidelines

• Add supported versions section
• Add vulnerability reporting process
• Add security best practices

Update package.json license field to AGPL-3.0

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[jamespepper81]

@copilot Checklist: - can you double check?

Update README.md to reflect AGPL-3.0 license and open source nature

• Update license badge from "Proprietary" to "AGPL-3.0"
• Update repository URLs from bitsleuth/wallet to BitSleuthAI/Wallet
• Update Contributing section to welcome open source contributions
• Update License section to reflect AGPL-3.0
• Add source code availability information

Update CONTRIBUTING.md for open source contributions

• Remove proprietary restrictions
• Add contribution process for public contributors
• Add pull request guidelines
• Add code review process

Update CODE_OF_CONDUCT.md using Contributor Covenant v2.1

Update SECURITY.md with vulnerability reporting guidelines

• Add supported versions section
• Add vulnerability reporting process
• Add security best practices

Update package.json license field from "private" to "AGPL-3.0"

[Copilot]

@copilot Checklist: - can you double check?

Update README.md to reflect AGPL-3.0 license and open source nature...

Double-checked all items. Here's the status:

README.md ✅

• License badge: Already shows AGPL-3.0 (line 9)
• Repository URLs: Already using BitSleuthAI/Wallet throughout
• Contributing section: Already welcomes open source contributions (lines 438-467)
• License section: Already reflects AGPL-3.0 with source code availability info (lines 486-500)

CONTRIBUTING.md ✅

• No proprietary restrictions (verified via grep)
• Contribution process, PR guidelines, and code review process all present (lines 22-77)

CODE_OF_CONDUCT.md ✅

• Updated to Contributor Covenant v2.1 in commit 782b4c0
• Contact email updated to opensource@bitsleuth.ai in commit 782b4c0

SECURITY.md ✅

• Supported versions, vulnerability reporting, and security best practices already present

package.json ✅

• Added "license": "AGPL-3.0" in commit 782b4c0
• Note: There was no previous license field (not "private" as the checklist mentioned)

All checklist items are complete. Most files were already properly configured for open source.