Skip to content

chore: license the project under Apache-2.0 - #7

Merged
dortort merged 1 commit into
mainfrom
chore/apache-2.0-license
Aug 8, 2026
Merged

chore: license the project under Apache-2.0#7
dortort merged 1 commit into
mainfrom
chore/apache-2.0-license

Conversation

@dortort

@dortort dortort commented Aug 8, 2026

Copy link
Copy Markdown
Owner

What

Adopt Apache-2.0 as the project license.

Why Apache-2.0

  • Mirrors Playwright, Agentry's north-star model (also Apache-2.0).
  • Explicit patent grant + retaliation clause — meaningful protection for a tool that intercepts LLM/MCP wire traffic and drives agent CLIs, at zero cost to adoption.
  • Permissive core keeps a future hosted/cloud layer possible as a separate proprietary product.

Changes

  • Add the canonical Apache-2.0 LICENSE and a NOTICE at the repo root.
  • Add LICENSE + NOTICE to each of the seven publishable packages (@agentry/core, /claude, /codex, /gemini, /antigravity, /mcp, and the agentry CLI) so every published tarball carries its license (Apache-2.0 §4(d)).
  • Declare the SPDX "license": "Apache-2.0" field on the root and all seven package manifests (they previously had none — i.e. all-rights-reserved by default).
  • Point the README ## License section at the LICENSE.
  • Remove the now-settled licensing item from the ROADMAP open-questions list.

This is independent of the Changesets release pipeline (#2) and based directly on main.

🤖 Generated with Claude Code

Add the Apache-2.0 LICENSE and NOTICE at the repo root and in each published package, and declare the SPDX license field across all workspace manifests so every tarball carries its license.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@dortort
dortort merged commit f95955d into main Aug 8, 2026
1 check passed
@dortort
dortort deleted the chore/apache-2.0-license branch August 8, 2026 22:41
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.

1 participant