rein-engine 0.1.1__tar.gz

rein_engine-0.1.1/.github/workflows/ci.yml

@@ -0,0 +1,38 @@
+name: CI
+
+on: [push, pull_request]
+
+jobs:
+  verify:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+      - run: pip install -e . pytest
+      - run: pytest -q
+      - run: rein review src/
+      - run: rein commit-check
+
+  action:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read  # checkout only; upload:false below needs no other scope
+    steps:
+      - uses: actions/checkout@v4
+      - name: Self-test the GitHub Action (review + SARIF, no upload)
+        # upload:false: code scanning (Security tab) needs GitHub Advanced
+        # Security, absent on this private repo. The self-test proves the action
+        # installs rein, runs review, and emits valid SARIF; the Security-tab
+        # upload is a consumer-side concern exercised on repos that have it.
+        uses: ./
+        with:
+          path: src/
+          upload: false
+      - name: Assert SARIF was produced and is valid
+        run: |
+          test -s rein.sarif
+          python -c "import json,sys; d=json.load(open('rein.sarif')); assert d.get('version')=='2.1.0', d.get('version'); assert d['runs'][0]['tool']['driver']['name']=='rein'; print('SARIF valid:', len(d['runs'][0].get('results', [])), 'results')"

rein_engine-0.1.1/.github/workflows/publish.yml

@@ -0,0 +1,76 @@
+name: Publish to PyPI
+
+# Trusted publishing (OIDC) - no stored API token. Configure a trusted publisher
+# on PyPI and TestPyPI for this repository and this workflow file. A manual run
+# publishes to TestPyPI (a dry run); publishing a GitHub Release publishes to PyPI.
+on:
+  release:
+    types: [published]
+  workflow_dispatch:
+    inputs:
+      target:
+        description: "Package index to publish to"
+        type: choice
+        options:
+          - testpypi
+          - pypi
+        default: testpypi
+
+jobs:
+  build:
+    # Guard so the workflow only runs in this repository, never in a fork.
+    if: github.repository == 'SametAtas/rein'
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+      - name: Build and check sdist + wheel
+        run: |
+          python -m pip install --upgrade build twine
+          python -m build
+          twine check dist/*
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  testpypi:
+    needs: build
+    if: >-
+      github.repository == 'SametAtas/rein'
+      && github.event_name == 'workflow_dispatch'
+      && inputs.target == 'testpypi'
+    runs-on: ubuntu-latest
+    permissions:
+      id-token: write  # OIDC: mint the short-lived token the index trusts
+      contents: read
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          repository-url: https://test.pypi.org/legacy/
+
+  pypi:
+    needs: build
+    if: >-
+      github.repository == 'SametAtas/rein'
+      && (github.event_name == 'release'
+          || (github.event_name == 'workflow_dispatch' && inputs.target == 'pypi'))
+    runs-on: ubuntu-latest
+    environment: pypi  # one-time: create this env on the public repo for an approval gate
+    permissions:
+      id-token: write
+      contents: read
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@release/v1

rein_engine-0.1.1/.gitignore

@@ -0,0 +1,14 @@
+__pycache__/
+*.py[cod]
+*.egg-info/
+build/
+dist/
+.venv/
+venv/
+.env
+.env.*
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.coverage
+htmlcov/

rein_engine-0.1.1/AGENTS.md

@@ -0,0 +1,151 @@
+# AGENTS.md
+
+Operating guide for AI agents (and humans) contributing to **rein**. Read this
+fully before editing. It is the contract that keeps the codebase coherent across
+multiple contributors who never talk to each other directly.
+
+## What this project is
+
+`rein` detects secrets, unsafe-code patterns, clean-code lint issues, and
+commit hygiene; turns findings into a policy verdict with remediation guidance;
+reviews whole files or diffs; and drives an agent steering loop -- usable from
+the CLI, an MCP server, or a git hook. It must stay **agent-agnostic**:
+usable from any agent or CI system, never tied to one host.
+
+## The one architectural rule
+
+> **`core/` thinks. Adapters do I/O.**
+
+- `src/rein/core/` contains pure functions. No printing, no `sys.exit`, no
+  subprocess, no network, no reading global state. Every check returns a list of
+  `Finding` objects (see `core/findings.py`).
+- `cli/`, `mcp/`, `hooks/` are **thin adapters**. They gather input (files, git,
+  JSON), call `core`, render the `Finding`s, and pick an exit code. They contain
+  no detection logic.
+
+If you are about to put a regex or a rule inside an adapter, stop. It belongs in
+`core/`, where every other interface can reuse it and a unit test can reach it
+without spawning a process.
+
+## Code style: the anti-slop charter
+
+We want a repo that reads like one careful engineer wrote it, not a generator.
+
+1. **Type-hint everything.** Public functions have full annotations. `from
+   __future__ import annotations` at the top of each module.
+2. **Docstrings explain *why*, not *what*.** A docstring that restates the
+   function name ("`scan_file`: scans a file") is noise; delete it. Document
+   intent, edge cases, and the contract.
+3. **Plain ASCII only, no emojis, anywhere.** No emojis, em-dashes, smart
+   quotes, arrows, or decorative symbols (such as check marks) in code, docs,
+   comments, CLI output, or commit messages. Use `-`, `:`, or rephrase. The
+   ASCII self-check below must print nothing. Comments mark non-obvious
+   decisions only; code that needs a comment to be readable should be rewritten.
+4. **Small files, small functions.** If a module passes ~250 lines or a function
+   passes ~50, it probably wants splitting. Limits are guidelines -- split where
+   there is a real seam, but do not fragment a cohesive module just to hit a
+   number (that is its own slop; see rule 7). Prefer clarity over cleverness.
+5. **Standard library first.** Add a dependency only when it earns its place;
+   justify it in the PR. `core` should stay dependency-free.
+6. **Match the surrounding code.** Naming, structure, and idiom should be
+   indistinguishable from the existing modules.
+7. **No dead scaffolding.** Don't commit `TODO`-stubs, empty handlers, or
+   "future-proofing" abstractions with one caller.
+8. **No marketing prose.** Docs and READMEs are terse and factual. No selling,
+   no metaphors, no filler adjectives.
+
+## Performance and resilience
+
+rein is called everywhere, including agent loops that invoke it repeatedly, so
+it must stay fast and hard to break.
+
+1. Zero or minimal runtime dependencies. `core` stays dependency-free; stdlib first.
+2. No redundant work. Parse a source once and share the AST across checks; keep
+   every check O(n) in input size.
+3. Bound, do not blow up. Malformed, huge, or hostile input degrades gracefully
+   (return findings or empty, never crash). Parsing catches SyntaxError,
+   ValueError, and RecursionError.
+4. Treat latency as a feature. The hot path is review/review_diff; the
+   perf-contract test asserts review parses the AST once.
+5. External detectors run with a strict timeout and fail open to prevent hanging the review.
+
+## Testing (non-negotiable)
+
+- Every new behavior in `core/` ships with a `pytest` test in `tests/`.
+- Tests must be deterministic and not touch the network.
+- Test files are exempt from type-hint and future-import lint rules; `rein review .` warning on them is by design, while `rein review src/` is the clean gate.
+- Run before every commit:
+  ```bash
+  pytest -q
+  ```
+- A change with failing or missing tests is not done.
+
+## Commits & security
+
+We dogfood our own tool. Before committing, run all three and make sure they
+are clean:
+```bash
+pytest -q
+rein scan .
+git ls-files | xargs grep -nP '[^\x00-\x7F]'   # must print nothing: ASCII only
+git ls-files | xargs grep -nP ' +$'            # must print nothing: no trailing whitespace
+```
+- Commit messages follow **Conventional Commits** (`feat:`, `fix:`, `docs:`,
+  `refactor:`, `test:`, `chore:`), imperative mood, subject <= 72 chars. Keep
+  them short and plain: one line, no multi-clause descriptions.
+- **No tool or AI attribution trailers.** Never add `Co-Authored-By` or any
+  tool or AI credit. A Developer Certificate of Origin `Signed-off-by:` line
+  (the human author certifying origin, via `git commit -s`) is allowed and is
+  required for outside contributions; see `CONTRIBUTING.md`. It is not an
+  attribution trailer.
+- **Never commit secrets or personal data**: no API keys, tokens, `.env` files,
+  emails, home paths, or machine-specific config. `rein scan` must pass clean.
+
+## How contributions are coordinated
+
+Contributors do not share a chat. The repo is the shared memory:
+
+- **Architecture & contracts** (the `Finding` shape, module boundaries, public
+  function signatures, the tests that define correct behavior) are authored by
+  the lead and committed first. Treat committed signatures and tests as fixed.
+- **Implementation tasks** are picked up against those contracts. The job is to
+  make the specified tests pass without changing the contract. If a contract
+  seems wrong, leave it and raise it; don't silently rewrite it.
+- When you finish a task: run `pytest -q` and `rein scan .`, then write a
+  Conventional-Commit message describing only what you changed.
+
+## Keeping the docs current
+
+The repo is the shared memory: anyone should be able to continue without a chat.
+When you finish a slice, update the project's durable docs in the same commit, so
+the status and the reasoning behind a choice stay current. Keep them in the
+project's voice: terse, factual, ASCII, no marketing. They capture intent,
+status, and reasoning that the code and git log do not.
+
+## Project layout
+
+```text
+src/rein/
+  core/      pure logic: findings, diffs, secrets, security, lint, commits, code,
+             review, remediation, baseline, config, conventions, drift, junk,
+             ruff/bandit/gitleaks/semgrep adapters, sarif, custom
+  loop.py    agent-loop driver (pure; agent injected)
+  cli/       argparse adapter
+  mcp/       MCP server adapter
+  hooks/     git pre-commit adapter
+tests/       pytest, one file per core module
+examples/    runnable agent integrations
+```
+
+## Dev setup
+
+```bash
+pip install -e ".[dev]"            # editable install + pytest
+pytest -q                          # run tests
+rein scan .                        # dogfood the scanner
+```
+
+rein dogfoods itself: `rein commit-check` rejects any commit message carrying AI
+or tool attribution (`Co-authored-by`, `generated by ...`) and flags tampering
+with rein's own config; CI runs it on every push. A human DCO `Signed-off-by:`
+line is allowed and is required for outside contributions.

rein_engine-0.1.1/CONTRIBUTING.md

@@ -0,0 +1,50 @@
+# Contributing to rein
+
+Thanks for your interest in rein. A few rules keep the codebase coherent, and
+contributions that ignore them will be asked to change:
+
+- Architecture: detection logic lives in pure functions under `rein.core` and
+  returns `Finding` objects. The CLI, MCP server, and git hooks are thin adapters
+  that gather input, call core, and render. No detection logic in adapters.
+- Style: type-hint everything, ASCII only (no emojis), keep files and functions
+  small, prefer the standard library, and include tests.
+- Commits: sole-authored, with a DCO sign-off (below). AI or tool attribution
+  trailers are not accepted.
+
+## License
+
+rein is licensed under the Apache License, Version 2.0 (see `LICENSE`). By
+contributing, you agree that your contributions are licensed under the same
+terms.
+
+## Developer Certificate of Origin (sign-off required)
+
+This project uses the Developer Certificate of Origin (see `DCO`). Every commit
+must be signed off, certifying that you wrote the change or have the right to
+submit it under the project license. Add the sign-off with:
+
+```bash
+git commit -s -m "feat: your change"
+```
+
+This appends a line of the form:
+
+```text
+Signed-off-by: Your Name <you@example.com>
+```
+
+The sign-off certifies the origin of the work. It is not a tool or AI
+attribution, which this project does not accept.
+
+## Before you open a pull request
+
+Run all three and make sure they are clean:
+
+```bash
+pytest -q
+rein scan .
+git ls-files | xargs grep -nP '[^\x00-\x7F]'   # must print nothing: ASCII only
+```
+
+Use Conventional Commit messages (`feat:`, `fix:`, `docs:`, `refactor:`,
+`test:`, `chore:`), one line, imperative mood, subject 72 chars or fewer.

rein_engine-0.1.1/DCO

@@ -0,0 +1,34 @@
+Developer Certificate of Origin
+Version 1.1
+
+Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
+
+Everyone is permitted to copy and distribute verbatim copies of this
+license document, but changing it is not allowed.
+
+
+Developer's Certificate of Origin 1.1
+
+By making a contribution to this project, I certify that:
+
+(a) The contribution was created in whole or in part by me and I
+    have the right to submit it under the open source license
+    indicated in the file; or
+
+(b) The contribution is based upon previous work that, to the best
+    of my knowledge, is covered under an appropriate open source
+    license and I have the right under that license to submit that
+    work with modifications, whether created in whole or in part
+    by me, under the same open source license (unless I am
+    permitted to submit under a different license), as indicated
+    in the file; or
+
+(c) The contribution was provided directly to me by some other
+    person who certified (a), (b) or (c) and I have not modified
+    it.
+
+(d) I understand and agree that this project and the contribution
+    are public and that a record of the contribution (including all
+    personal information I submit with it, including my sign-off) is
+    maintained indefinitely and may be redistributed consistent with
+    this project or the open source license(s) involved.

rein_engine-0.1.1/LICENSE

@@ -0,0 +1,201 @@
+                                 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 Abdulsamet Atas
+
+   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.

rein_engine-0.1.1/NOTICE

@@ -0,0 +1,4 @@
+rein
+Copyright 2026 Abdulsamet Atas
+
+This product is licensed under the Apache License, Version 2.0 (see LICENSE).