License: MIT to AGPL-3.0

[abdulsaheel]

Relicenses analytics from MIT to AGPL-3.0 (owner decision), with NOTICE (MIT up to the previous main commit), TRADEMARKS.md; contributions are licensed under AGPL-3.0 (no CLA).

Do not merge until contributor consent is collected (list kept privately by the owner) and a lawyer has reviewed CLA.md and TRADEMARKS.md. Earlier releases remain MIT.

🤖 Generated with Claude Code

Summary by Sourcery

Relicense the current OpenStrap codebase under AGPL-3.0 and establish contribution and trademark policies.

Enhancements:

• Relicense the current project from MIT to AGPL-3.0 while preserving prior-release licensing through a NOTICE file.
• Define contribution licensing terms and separate OpenStrap trademark usage requirements for forks and redistributed versions.

Documentation:

• Update project documentation and licensing badges to describe AGPL-3.0 licensing and trademark protections.

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

---

_{Comment @coderabbitai help to get the list of available commands.}

[sourcery-ai]

Reviewer's Guide

This PR changes the current project license from MIT to AGPL-3.0, documents the transition and historical MIT coverage, adds a broad contributor license agreement with explicit acceptance requirements, and establishes separate trademark guidance. It also updates repository documentation and terminology to reflect the new licensing and branding policy; merging is explicitly gated on contributor consent and legal review.

Sequence diagram for contributor CLA acceptance

sequenceDiagram
    actor Contributor
    participant PR as PullRequest
    participant Maintainer
    Contributor->>PR: Add CLA acceptance text
    PR->>Maintainer: Submit contribution
    Maintainer->>PR: Verify CLA acceptance
    PR-->>Maintainer: Future contributions covered by CLA

Loading

Flow diagram for the AGPL relicensing and contribution policy

flowchart TD
    A["Existing releases remain MIT"] --> B["Current project license becomes AGPL-3.0"]
    B --> C["Contributor reads CLA.md"]
    C --> D["Contributor adds CLA acceptance to first PR"]
    D --> E["Future contributions covered by CLA"]
    B --> F["Forks may use AGPL code"]
    F --> G["Forks use a different name and branding"]

Loading

File-Level Changes

Change	Details	Files
Relicense the project and document historical licensing and attribution.	Replace the MIT license with AGPL-3.0. Add a NOTICE file covering MIT-licensed material through the previous main commit. Update license references and badge in project documentation. Retain MIT licensing for earlier releases as described by the new notices.	LICENSE NOTICE README.md
Introduce contributor terms that grant broad relicensing and patent rights.	Add a CLA covering contributions across OpenStrap repositories. Require first-time contributors to provide an explicit acceptance statement. Grant rights to distribute contributions under AGPL, other open-source licenses, or commercial terms. Add contribution provenance, third-party licensing, and patent-related confirmations.	CLA.md CONTRIBUTING.md
Define project trademark usage and restrictions separately from the software license.	Reserve the OpenStrap name and logo while permitting AGPL code forks. Require modified distributions to use distinct names and branding and avoid implying endorsement. Document permitted descriptive references and disclaimers for third-party marks.	TRADEMARKS.md README.md
Adjust project language to remove vendor-specific reverse-engineering terminology.	Replace references to reverse-engineering vendor scores or byte streams with more general descriptions. Preserve the project’s disclaimer that its metrics are independent approximations.	CONTRIBUTING.md README.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.