From 3420426ac52c70bc787a8fd9b21ba58bbc963ab0 Mon Sep 17 00:00:00 2001 From: Binay <150876063+bkd-dotcom@users.noreply.github.com> Date: Mon, 31 Aug 2026 20:49:56 -0400 Subject: [PATCH] chore: relicense to Apache-2.0 (Signetry goes open core) Signetry moves to an open-core model. This repository is part of the integration surface, so it is now Apache-2.0: use it, fork it, ship it commercially, no permission needed. The engine (Signetry/core) is source-available under BUSL-1.1 and converts to Apache-2.0 on 2030-08-31. Until now every repo in the org was "All Rights Reserved" with no LICENSE file, which GitHub reports as no license at all. That is the strictest possible default: it blocks corporate evaluation outright and makes outside contribution legally murky. This fixes that. What changed: - LICENSE (Apache-2.0) added, so GitHub detects and displays it. - README, CONTRIBUTING, CLA, CONTRIBUTORS and the CLA bot comment no longer claim the project is "not open source" or withhold usage rights. - The CLA is kept, because open core means code moves across the licence line and relicensing needs those rights. Its fallback licence grant is now non-exclusive: the previous *exclusive* grant would have stripped contributors of the right to use their own contribution, contradicting the rights the LICENSE grants everyone. The CLA text is now identical across all Signetry repos so the legal terms cannot drift per-repo again. - Community health files (SECURITY.md, CODE_OF_CONDUCT.md, issue templates) where they were missing. No functional or API change. --- .github/ISSUE_TEMPLATE/bug_report.yml | 75 ++++++++ .github/ISSUE_TEMPLATE/config.yml | 14 ++ .github/ISSUE_TEMPLATE/feature_request.yml | 62 +++++++ .github/workflows/cla.yml | 11 +- .github/workflows/reviewer.yml | 2 +- CHANGELOG.md | 14 ++ CLA.md | 38 ++-- CONTRIBUTING.md | 91 +++++++++- CONTRIBUTORS.md | 14 +- LICENSE | 202 +++++++++++++++++++++ README.md | 15 +- 11 files changed, 504 insertions(+), 34 deletions(-) create mode 100644 .github/ISSUE_TEMPLATE/bug_report.yml create mode 100644 .github/ISSUE_TEMPLATE/config.yml create mode 100644 .github/ISSUE_TEMPLATE/feature_request.yml create mode 100644 LICENSE diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml new file mode 100644 index 0000000..6bb06d7 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/bug_report.yml @@ -0,0 +1,75 @@ +name: Bug report +description: The guard blocked something it should have allowed, allowed something it should have blocked, or crashed. +labels: ["bug"] +body: + - type: markdown + attributes: + value: | + Thanks for the report. Two things first: + + - **Policy semantics live in [signetry-core](https://github.com/Signetry/core).** + If the contract itself is being evaluated wrongly (scope, forbidden paths, + gates, receipts), file it there. This repo is the thin shell wrapper around + `signetry guard`. + - **Suspected vulnerability?** Do not open an issue — see + [SECURITY.md](https://github.com/Signetry/precommit/blob/main/SECURITY.md) + and use private reporting. + + - type: textarea + id: what-happened + attributes: + label: What happened + description: What did the guard do, and what did you expect instead? + validations: + required: true + + - type: dropdown + id: surface + attributes: + label: How was the guard invoked? + options: + - pre-commit hook (id: signetry-guard) + - universal/signetry-guard.sh --staged + - universal/signetry-guard.sh --path + - universal/signetry-guard.sh --command + - universal/signetry-guard.sh --stdin-json + - demos/try-guard.sh + - Other / not sure + validations: + required: true + + - type: textarea + id: repro + attributes: + label: Reproduction + description: The exact command you ran and its output. A minimal case is ideal. + render: shell + validations: + required: true + + - type: textarea + id: contract + attributes: + label: Your .signetry/admission.yaml + description: The relevant part of the contract in play. Redact anything sensitive. + render: yaml + + - type: textarea + id: versions + attributes: + label: Versions + description: | + Output of `signetry --version`, this repo's `rev:` or commit, `bash --version`, and your OS. + render: shell + validations: + required: true + + - type: checkboxes + id: checks + attributes: + label: Checks + options: + - label: "`signetry-core` is installed and `signetry` is on PATH (a missing binary fails open unless `SIGNETRY_GUARD_STRICT=1`)." + required: true + - label: I have read the note above and this is a wrapper bug, not core policy behavior. + required: false diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml new file mode 100644 index 0000000..ce2b05b --- /dev/null +++ b/.github/ISSUE_TEMPLATE/config.yml @@ -0,0 +1,14 @@ +blank_issues_enabled: false +contact_links: + - name: Governance engine (contracts, guard, verifier, receipts) + url: https://github.com/Signetry/core/issues + about: Policy semantics live in signetry-core. This repo is a thin wrapper over it. + - name: The enforced CI gate + url: https://github.com/Signetry/action/issues + about: The required Signetry Admission check on a pull request. + - name: Signetry platform (overview, licensing, roadmap) + url: https://github.com/Signetry/signetry + about: Cross-repo questions, and the open-core licensing model. + - name: Report a security vulnerability + url: https://github.com/Signetry/precommit/security/advisories/new + about: Private disclosure. Please never use a public issue for an unpatched vulnerability. diff --git a/.github/ISSUE_TEMPLATE/feature_request.yml b/.github/ISSUE_TEMPLATE/feature_request.yml new file mode 100644 index 0000000..84320c2 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/feature_request.yml @@ -0,0 +1,62 @@ +name: Feature request +description: Propose a change to the guard wrapper, the pre-commit hook contract, or the docs. +labels: ["enhancement"] +body: + - type: markdown + attributes: + value: | + This repo is **Apache-2.0** — proposals and PRs are welcome. See + [CONTRIBUTING.md](https://github.com/Signetry/precommit/blob/main/CONTRIBUTING.md). + + Two constraints shape what fits here: + + - **The guard is deterministic.** Every verdict comes from `signetry guard` and + your `.signetry/admission.yaml` — never from a model. + - **No policy reimplementation.** This repo pins `signetry-core` and defers to + it. Contract semantics belong in + [signetry-core](https://github.com/Signetry/core). + + - type: textarea + id: problem + attributes: + label: The problem + description: What can't you do today? Describe the situation, not the solution. + validations: + required: true + + - type: textarea + id: proposal + attributes: + label: Proposed change + validations: + required: true + + - type: dropdown + id: area + attributes: + label: Area + options: + - universal/signetry-guard.sh + - pre-commit hook contract (.pre-commit-hooks.yaml) + - demos + - Documentation + - CI / workflows + - Other + validations: + required: true + + - type: textarea + id: alternatives + attributes: + label: Alternatives considered + description: Including whether this belongs in `signetry-core` or another integration repo instead. + + - type: checkboxes + id: checks + attributes: + label: Checks + options: + - label: This does not require the guard to consult a model for a verdict. + required: true + - label: I'd be willing to open a PR for this (optional — no obligation). + required: false diff --git a/.github/workflows/cla.yml b/.github/workflows/cla.yml index 846eab2..65169d1 100644 --- a/.github/workflows/cla.yml +++ b/.github/workflows/cla.yml @@ -3,8 +3,13 @@ name: CLA # Requires every contributor to sign the Contributor License Agreement (CLA.md) # before their pull request can be merged. Runs entirely in this repo's Actions — # no third-party OAuth app. Signatures are recorded in signatures/cla.json on this -# repo, so there is a durable, auditable record that each contributor assigned -# copyright/ownership of their contribution to the Owner. +# repo, so there is a durable, auditable record of each contributor's assent. +# +# This repo is Apache-2.0. The CLA is kept because Signetry is open core: code moves +# across the line between this Apache-2.0 integration surface and the BUSL-1.1 engine +# (Signetry/core, which converts to Apache-2.0 on 2030-08-31), and the CLA supplies the +# relicensing rights that makes possible. It does not reduce a contributor's own +# Apache-2.0 rights. See CONTRIBUTING.md. # # A contributor signs by commenting the exact statement below on their PR: # I have read the CLA Document and I hereby sign the CLA @@ -48,7 +53,7 @@ jobs: path-to-document: "https://github.com/Signetry/precommit/blob/main/CLA.md" branch: "cla-signatures" allowlist: "dependabot[bot],bkd-dotcom" - custom-notsigned-prcomment: "Thanks for your contribution! Before it can be merged, please read the **[Contributor License Agreement](https://github.com/Signetry/precommit/blob/main/CLA.md)** — Signetry is **All Rights Reserved**, and by signing you assign copyright/ownership of your contribution to the Owner (you may not use, sell, or commercialize it yourself). To agree, reply with exactly:" + custom-notsigned-prcomment: "Thanks for your contribution! Before it can be merged, please read the **[Contributor License Agreement](https://github.com/Signetry/precommit/blob/main/CLA.md)** — this repo is **Apache-2.0**, and the CLA lets us relicense contributions across Signetry's [open-core boundary](https://github.com/Signetry/signetry/blob/main/LICENSING.md) (for example moving an adapter into the BUSL-1.1 engine). You keep every Apache-2.0 right to this code, including the right to use your own contribution anywhere. To agree, reply with exactly:" custom-pr-sign-comment: "I have read the CLA Document and I hereby sign the CLA" custom-allsigned-prcomment: "All contributors have signed the CLA. ✅" lock-pullrequest-aftermerge: false diff --git a/.github/workflows/reviewer.yml b/.github/workflows/reviewer.yml index d2fa824..410d0cd 100644 --- a/.github/workflows/reviewer.yml +++ b/.github/workflows/reviewer.yml @@ -34,7 +34,7 @@ jobs: with: python-version: "3.12" - name: Install signetry-reviewer - # source-available (All Rights Reserved); install from source, not PyPI. + # Not published to PyPI; install from source at a pinned git tag. run: pip install "signetry-reviewer @ git+https://github.com/Signetry/reviewer@v0.2.0" - name: Compute the PR diff env: diff --git a/CHANGELOG.md b/CHANGELOG.md index 21b391f..6228c15 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -6,9 +6,23 @@ Follows [Keep a Changelog](https://keepachangelog.com/) / [SemVer](https://semve ### Changed +- **Licence: this repository is now [Apache-2.0](LICENSE)** (previously + all-rights-reserved / source-available). Signetry has moved to an open-core model: + the integration surface — this repo, the GitHub Action, the editor and agent plugins, + the eval suite — is Apache-2.0, while the engine + ([`signetry-core`](https://github.com/Signetry/core)) is BUSL-1.1 and converts to + Apache-2.0 on 2030-08-31. The CLA is retained so contributions can be relicensed + across that boundary; it does not reduce anyone's Apache-2.0 rights. See + [CONTRIBUTING.md](CONTRIBUTING.md). - Signetry naming: CLI `signetry`, env `SIGNETRY_*`, config `.signetry/`, package `signetry-core`, and the sibling `signetry-reviewer`. The guard script is `universal/signetry-guard.sh` and the pre-commit hook `id` is `signetry-guard`. +- **The CLA's fallback licence grant is now non-exclusive.** It previously granted the + Owner an *exclusive* licence where copyright assignment is not permitted by law, which + would have stripped contributors of the right to use their own contribution — directly + contradicting the rights the LICENSE grants everyone. The CLA text is now identical + across all Signetry repositories (bar the engine/integration licence wording) so the + legal terms cannot drift per-repo again. See [CLA.md](CLA.md) §2–3. ## [0.3.0] — 2026-07-26 diff --git a/CLA.md b/CLA.md index 07c0cbc..f89b32e 100644 --- a/CLA.md +++ b/CLA.md @@ -1,6 +1,10 @@ # Signetry Contributor License Agreement (CLA) -**Copyright (c) 2026 Binay Dalai. All rights reserved.** +**Copyright (c) 2026 Binay Dalai.** This repository is licensed under +**[Apache-2.0](LICENSE)** as part of Signetry's +[open-core model](https://github.com/Signetry/signetry/blob/main/LICENSING.md). This +Agreement governs what You grant the Owner when You contribute; it does not reduce the +rights the Apache-2.0 licence gives You (and everyone else) in this code. Thank you for your interest in contributing to Signetry ("the Project"), owned by Binay Dalai ("the Owner"). This Contributor License Agreement ("Agreement") @@ -26,21 +30,33 @@ Your Contribution. You agree that the Owner is the sole and exclusive owner of t Contribution once merged into the Project. To the extent any rights cannot be assigned by law, You grant the Owner a -**perpetual, worldwide, exclusive, irrevocable, royalty-free, sublicensable, and +**perpetual, worldwide, non-exclusive, irrevocable, royalty-free, sublicensable, and transferable license** to use, reproduce, modify, prepare derivative works of, publicly display, publicly perform, distribute, **sell, and commercialize** Your Contribution, in whole or in part, in any form and for any purpose. -## 3. The Owner's exclusive rights +Nothing in this section removes Your own ability to use Your Contribution: once it is +released as part of this repository it is available to You, as to anyone, under +[Apache-2.0](LICENSE), and You retain any rights You independently hold in the +underlying ideas and techniques. + +## 3. Why the Owner needs this (open core) You acknowledge and agree that: -- The Owner alone retains the right to **use, license, sell, and monetize** the - Project, including Your Contribution. -- You obtain **no right** to use, copy, modify, distribute, sell, or commercialize - the Project or Your Contribution for Your own personal or commercial purposes, - except as expressly permitted in writing by the Owner. -- The Project is **not open source** and is licensed "All Rights Reserved." +- **You keep the licence's rights.** This repository is released under + [Apache-2.0](LICENSE), so You may use, copy, modify, distribute, and commercialize + it — including Your own Contribution — on exactly the same terms as any other user. + No separate written permission is required. +- **The Owner may relicense.** The assignment above lets the Owner use, license, sell, + and monetize the Project, including Your Contribution, and release it under other + terms. +- **Code may move across the open-core line.** Signetry's integration surface is + Apache-2.0 while the engine + ([`Signetry/core`](https://github.com/Signetry/core)) is source-available under + BUSL-1.1, converting to Apache-2.0 on 2030-08-31. A Contribution accepted here may + later be moved into the engine, or engine code moved out to an Apache-2.0 repo. The + CLA is what makes that possible without asking every past contributor again. ## 4. Recognition of Contributors (credit, not rights) @@ -50,8 +66,8 @@ of Your work. This recognition is **attribution only**. It does **not**: -- grant You any ownership, license, or right to use, copy, sell, sublicense, or - commercialize the Project or Your Contribution; +- grant You ownership of the Project, or any rights beyond those the Project's + licence already grants everyone; - entitle You to represent the Project, or any part of it, as Your own work, product, or property, or to market or sell it under Your own name or brand; or - create any partnership, employment, or revenue-sharing relationship with the Owner. diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 9f91869..7bc2640 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1,6 +1,31 @@ -# Contribution Agreement +# Contributing to signetry-precommit -By submitting a Pull Request to this repository, you agree to assign and transfer all copyright and ownership of your contributed code to the repository owner. The owner retains the exclusive right to monetize, use, and control the entire codebase. +This repository is **[Apache-2.0](LICENSE)**. You may use, copy, modify, distribute, +and commercialize it — including in closed-source and commercial products — with no +permission needed and no fee. Contributions are very welcome. + +## Licensing, in short + +- **The code here is Apache-2.0.** Fork it, vendor it, ship it. Attribution and the + licence notice are the only obligations, per the [LICENSE](LICENSE). +- **A signed CLA is still required before a PR merges** (see below). That is not a + walk-back of the open licence — it is what keeps the open-core boundary movable. +- This repo is the *integration surface*. The engine + ([`signetry-core`](https://github.com/Signetry/core)) is source-available under + BUSL-1.1 and converts to Apache-2.0 on **2030-08-31**. See the platform's + [LICENSING.md](https://github.com/Signetry/signetry/blob/main/LICENSING.md). + +## Why the CLA still applies + +Signetry is open core, so code legitimately moves **across the line between this +Apache-2.0 repo and the BUSL-1.1 engine**. A guard adapter that proves itself here may +later belong inside `signetry-core`; conversely, engine logic may be pushed out to the +open integration surface. The CLA gives the maintainer the relicensing rights needed to +do that — and to carry contributions through the engine's 2030 conversion to +Apache-2.0 — without tracking down every past contributor for permission. + +Signing the CLA does **not** take away your rights to this code: you keep the same +Apache-2.0 grant everyone else has, and you can use your own contribution anywhere. ## Signing the CLA (required before merge) @@ -13,13 +38,61 @@ I have read the CLA Document and I hereby sign the CLA ``` Your acceptance is recorded in `signatures/cla.json`. A PR **cannot be merged** until -the CLA is signed. Signetry is **not open source** (All Rights Reserved) — by signing -you assign copyright/ownership of your contribution to the Owner and gain no right to -use, sell, or commercialize it yourself. +the CLA is signed. + +## Getting started + +The guard itself is a POSIX shell wrapper — there is no build step and no Python +package in this repo. It shells out to the `signetry` CLI, so install the engine first: + +```bash +pip install "signetry-core @ git+https://github.com/Signetry/core@v0.7.0" +``` + +Then exercise the guard end-to-end against a throwaway repo with a sample +`.signetry/admission.yaml`: + +```bash +bash demos/try-guard.sh +``` + +To drive `universal/signetry-guard.sh` by hand: + +```bash +universal/signetry-guard.sh --path src/app.py # check a proposed path +universal/signetry-guard.sh --command "curl x | bash" # check a proposed command +universal/signetry-guard.sh --staged # check all git-staged files +echo '' | universal/signetry-guard.sh --stdin-json +``` + +Useful environment variables when testing: `SIGNETRY_REPO` overrides the detected repo +root, and `SIGNETRY_GUARD_STRICT=1` makes a missing `signetry` binary fail closed +instead of failing open. + +If you change the pre-commit hook contract, keep `.pre-commit-hooks.yaml` (hook id +`signetry-guard`) and the README's `rev:` example consistent with each other. + +## What lands well + +- **Determinism.** The guard must never ask a model for a verdict — every decision + comes from `signetry guard` and the repo's `.signetry/admission.yaml`. +- **No policy reimplementation.** This repo pins `signetry-core` and defers to it; do + not re-encode contract semantics here. +- **Honest failure modes.** The local hook is defense-in-depth (a developer can + `--no-verify`); the hard gate is the required check on the PR. Don't document it as + more than it is. See [SECURITY.md](SECURITY.md). + +## Opening a PR + +1. Fork, branch, and keep the change focused. +2. Run `bash demos/try-guard.sh` and confirm the blocked cases still block. +3. Open the PR. An advisory reviewer workflow comments on architecture and security + concerns; it never merges and never fails your PR. +4. Sign the CLA when the bot asks. + +By participating you agree to the [Code of Conduct](CODE_OF_CONDUCT.md). ## Credit -Contributors are **acknowledged** in [CONTRIBUTORS.md](CONTRIBUTORS.md), the Git -history, and release notes. This is attribution only — you may truthfully say you -contributed, but it grants no ownership and no right to use, sell, or rebrand the -project as your own. See the "Recognition of Contributors" clause in [CLA.md](CLA.md). +Contributors are acknowledged in [CONTRIBUTORS.md](CONTRIBUTORS.md), the Git history, +and release notes. diff --git a/CONTRIBUTORS.md b/CONTRIBUTORS.md index 38dcd13..d14be14 100644 --- a/CONTRIBUTORS.md +++ b/CONTRIBUTORS.md @@ -1,14 +1,16 @@ # Contributors -Signetry is **owned by Binay Dalai** and is **All Rights Reserved** (not open source). +This repository is **[Apache-2.0](LICENSE)** and maintained by Binay Dalai as part of +Signetry's [open-core model](https://github.com/Signetry/signetry/blob/main/LICENSING.md). The people below are gratefully acknowledged for contributions accepted under the [Contributor License Agreement](CLA.md). -**Credit, not ownership.** Being listed here recognizes a person's contribution. It -does **not** grant any right to use, copy, sell, sublicense, or commercialize the -project, and does **not** entitle anyone to present the project (in whole or in part) -as their own work, product, or brand. All such rights remain exclusively with the -owner. +**Credit, not ownership.** Being listed here recognizes a person's contribution. +Everyone — contributors included — already has the right to use, modify, and +commercialize this code under Apache-2.0. Listing here does **not** additionally grant +ownership of the project, and does **not** entitle anyone to present the project (in +whole or in part) as their own work, product, or brand, or to use the Signetry name to +endorse their own products. ## Owner / maintainer diff --git a/LICENSE b/LICENSE new file mode 100644 index 0000000..118c83c --- /dev/null +++ b/LICENSE @@ -0,0 +1,202 @@ + Apache License + Version 2.0, January 2004 + http://www.apache.org/licenses/ + + TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION + + 1. Definitions. + + "License" shall mean the terms and conditions for use, reproduction, + and distribution as defined by Sections 1 through 9 of this document. + + "Licensor" shall mean the copyright owner or entity authorized by + the copyright owner that is granting the License. + + "Legal Entity" shall mean the union of the acting entity and all + other entities that control, are controlled by, or are under common + control with that entity. For the purposes of this definition, + "control" means (i) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (ii) ownership of fifty percent (50%) or more of the + outstanding shares, or (iii) beneficial ownership of such entity. + + "You" (or "Your") shall mean an individual or Legal Entity + exercising permissions granted by this License. + + "Source" form shall mean the preferred form for making modifications, + including but not limited to software source code, documentation + source, and configuration files. + + "Object" form shall mean any form resulting from mechanical + transformation or translation of a Source form, including but + not limited to compiled object code, generated documentation, + and conversions to other media types. + + "Work" shall mean the work of authorship, whether in Source or + Object form, made available under the License, as indicated by a + copyright notice that is included in or attached to the work + (an example is provided in the Appendix below). + + "Derivative Works" shall mean any work, whether in Source or Object + form, that is based on (or derived from) the Work and for which the + editorial revisions, annotations, elaborations, or other modifications + represent, as a whole, an original work of authorship. For the purposes + of this License, Derivative Works shall not include works that remain + separable from, or merely link (or bind by name) to the interfaces of, + the Work and Derivative Works thereof. + + "Contribution" shall mean any work of authorship, including + the original version of the Work and any modifications or additions + to that Work or Derivative Works thereof, that is intentionally + submitted to Licensor for inclusion in the Work by the copyright owner + or by an individual or Legal Entity authorized to submit on behalf of + the copyright owner. For the purposes of this definition, "submitted" + means any form of electronic, verbal, or written communication sent + to the Licensor or its representatives, including but not limited to + communication on electronic mailing lists, source code control systems, + and issue tracking systems that are managed by, or on behalf of, the + Licensor for the purpose of discussing and improving the Work, but + excluding communication that is conspicuously marked or otherwise + designated in writing by the copyright owner as "Not a Contribution." + + "Contributor" shall mean Licensor and any individual or Legal Entity + on behalf of whom a Contribution has been received by Licensor and + subsequently incorporated within the Work. + + 2. Grant of Copyright License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + copyright license to reproduce, prepare Derivative Works of, + publicly display, publicly perform, sublicense, and distribute the + Work and such Derivative Works in Source or Object form. + + 3. Grant of Patent License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + (except as stated in this section) patent license to make, have made, + use, offer to sell, sell, import, and otherwise transfer the Work, + where such license applies only to those patent claims licensable + by such Contributor that are necessarily infringed by their + Contribution(s) alone or by combination of their Contribution(s) + with the Work to which such Contribution(s) was submitted. If You + institute patent litigation against any entity (including a + cross-claim or counterclaim in a lawsuit) alleging that the Work + or a Contribution incorporated within the Work constitutes direct + or contributory patent infringement, then any patent licenses + granted to You under this License for that Work shall terminate + as of the date such litigation is filed. + + 4. Redistribution. You may reproduce and distribute copies of the + Work or Derivative Works thereof in any medium, with or without + modifications, and in Source or Object form, provided that You + meet the following conditions: + + (a) You must give any other recipients of the Work or + Derivative Works a copy of this License; and + + (b) You must cause any modified files to carry prominent notices + stating that You changed the files; and + + (c) You must retain, in the Source form of any Derivative Works + that You distribute, all copyright, patent, trademark, and + attribution notices from the Source form of the Work, + excluding those notices that do not pertain to any part of + the Derivative Works; and + + (d) If the Work includes a "NOTICE" text file as part of its + distribution, then any Derivative Works that You distribute must + include a readable copy of the attribution notices contained + within such NOTICE file, excluding those notices that do not + pertain to any part of the Derivative Works, in at least one + of the following places: within a NOTICE text file distributed + as part of the Derivative Works; within the Source form or + documentation, if provided along with the Derivative Works; or, + within a display generated by the Derivative Works, if and + wherever such third-party notices normally appear. The contents + of the NOTICE file are for informational purposes only and + do not modify the License. You may add Your own attribution + notices within Derivative Works that You distribute, alongside + or as an addendum to the NOTICE text from the Work, provided + that such additional attribution notices cannot be construed + as modifying the License. + + You may add Your own copyright statement to Your modifications and + may provide additional or different license terms and conditions + for use, reproduction, or distribution of Your modifications, or + for any such Derivative Works as a whole, provided Your use, + reproduction, and distribution of the Work otherwise complies with + the conditions stated in this License. + + 5. Submission of Contributions. Unless You explicitly state otherwise, + any Contribution intentionally submitted for inclusion in the Work + by You to the Licensor shall be under the terms and conditions of + this License, without any additional terms or conditions. + Notwithstanding the above, nothing herein shall supersede or modify + the terms of any separate license agreement you may have executed + with Licensor regarding such Contributions. + + 6. Trademarks. This License does not grant permission to use the trade + names, trademarks, service marks, or product names of the Licensor, + except as required for reasonable and customary use in describing the + origin of the Work and reproducing the content of the NOTICE file. + + 7. Disclaimer of Warranty. Unless required by applicable law or + agreed to in writing, Licensor provides the Work (and each + Contributor provides its Contributions) on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + implied, including, without limitation, any warranties or conditions + of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A + PARTICULAR PURPOSE. You are solely responsible for determining the + appropriateness of using or redistributing the Work and assume any + risks associated with Your exercise of permissions under this License. + + 8. Limitation of Liability. In no event and under no legal theory, + whether in tort (including negligence), contract, or otherwise, + unless required by applicable law (such as deliberate and grossly + negligent acts) or agreed to in writing, shall any Contributor be + liable to You for damages, including any direct, indirect, special, + incidental, or consequential damages of any character arising as a + result of this License or out of the use or inability to use the + Work (including but not limited to damages for loss of goodwill, + work stoppage, computer failure or malfunction, or any and all + other commercial damages or losses), even if such Contributor + has been advised of the possibility of such damages. + + 9. Accepting Warranty or Additional Liability. While redistributing + the Work or Derivative Works thereof, You may choose to offer, + and charge a fee for, acceptance of support, warranty, indemnity, + or other liability obligations and/or rights consistent with this + License. However, in accepting such obligations, You may act only + on Your own behalf and on Your sole responsibility, not on behalf + of any other Contributor, and only if You agree to indemnify, + defend, and hold each Contributor harmless for any liability + incurred by, or claims asserted against, such Contributor by reason + of your accepting any such warranty or additional liability. + + END OF TERMS AND CONDITIONS + + APPENDIX: How to apply the Apache License to your work. + + To apply the Apache License to your work, attach the following + boilerplate notice, with the fields enclosed by brackets "[]" + replaced with your own identifying information. (Don't include + the brackets!) The text should be enclosed in the appropriate + comment syntax for the file format. We also recommend that a + file or class name and description of purpose be included on the + same "printed page" as the copyright notice for easier + identification within third-party archives. + + Copyright 2026 Binay Dalai + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. + diff --git a/README.md b/README.md index 542e768..a7b7fb8 100644 --- a/README.md +++ b/README.md @@ -1,8 +1,7 @@ # signetry-precommit -> **Copyright (c) 2026 Binay Dalai. All rights reserved.** -> This repository is strictly for viewing and contributing to the original project. You may not use, copy, modify, distribute, or commercialize this code for your own personal or commercial projects without explicit written permission. Only the original author retains the right to use and monetize this project. - +[![License](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](LICENSE) +[![PRs welcome (CLA)](https://img.shields.io/badge/PRs-welcome%20(CLA)-brightgreen.svg)](CONTRIBUTING.md) **Govern coding-agent changes at the git boundary — pre-commit, pre-push, or CI.** @@ -56,4 +55,12 @@ receipt, and `auto_merge` is always false — a human merges. ## License -**Copyright (c) 2026 Binay Dalai. All rights reserved.** This code is not open source. You may not use, copy, modify, distribute, or commercialize it for your own personal or commercial purposes without explicit written permission from the author, who alone retains the right to use and monetize this project. See [CONTRIBUTING.md](CONTRIBUTING.md). +[Apache-2.0](LICENSE). Use it, fork it, ship it commercially — no strings. + +This repository is part of Signetry's [open-core model](https://github.com/Signetry/signetry/blob/main/LICENSING.md): +the **integration surface is Apache-2.0** so anyone can add an agent, an editor, or a +CI adapter, while the engine ([`Signetry/core`](https://github.com/Signetry/core)) is +source-available under BUSL-1.1 and converts to Apache-2.0 on 2030-08-31. + +Contributions are accepted under the [CLA](CLA.md) — it lets us move a well-built +adapter into the engine later without asking every contributor for permission again.