limes-guard 0.17.1__tar.gz

limes_guard-0.17.1/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,40 @@
+---
+name: Bug report
+about: A defect in the limes engine, a detector, or a transport
+title: "bug: "
+labels: bug
+---
+
+**Do not use this for security vulnerabilities.** See
+[SECURITY.md](../../SECURITY.md) for private reporting.
+
+## What happened
+
+A clear description of the bug.
+
+## Reproduce
+
+Minimal steps or a code snippet. If it involves a detector verdict, include the
+input and the `Verdict` / `Evidence` you observed.
+
+```python
+# minimal repro
+```
+
+## Expected
+
+What you expected instead (e.g. `Deny` with evidence, `CannotSay`, `Allow`).
+
+## Environment
+
+- limes version / commit:
+- Python version:
+- OS:
+
+## Which layer (best guess)
+
+- [ ] Core (verdict algebra, evidence chain)
+- [ ] Detector / policy
+- [ ] Transport
+- [ ] Eval harness
+- [ ] Docs

limes_guard-0.17.1/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,30 @@
+---
+name: Feature request
+about: Propose a new detector, policy, or transport (the core never grows)
+title: "feat: "
+labels: enhancement
+---
+
+## What and why
+
+What capability is missing, and the problem it solves.
+
+## Which layer (ADR 0004)
+
+A new capability is a plugin, never a change to the core.
+
+- [ ] Detector (new detection capability)
+- [ ] Policy (new rules for an existing detector)
+- [ ] Transport (new integration surface — MCP, HTTP, …)
+- [ ] Something that seems to need a core change → it needs a new ADR; say why
+
+## If this is a detector: the admission rule (ADR 0003)
+
+A detector ships only with its **two numbers**. Sketch how you would measure it:
+
+- **Positive corpus** — the attacks it catches:
+- **Benign corpus** — legitimate traffic it must not kill:
+- **Null control** — how it beats doing nothing, and how it avoids block-everything:
+
+A detector without a benign corpus and a null control will not be admitted,
+however easy it looks.

limes_guard-0.17.1/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,20 @@
+## What this changes
+
+A short description, and the motivation. Link any issue or ADR.
+
+## Checklist
+
+- [ ] `make gate` is green locally (ruff + ruff format --check + mypy --strict + pytest).
+- [ ] Commits follow **Conventional Commits** (`feat:`, `fix:`, `docs:`, …).
+- [ ] Structural change? It references or adds an ADR under `docs/decisions/`.
+- [ ] I have signed the [CLA](CLA.md) (required before a first merge).
+
+## If this adds or changes a detector (ADR 0003)
+
+- [ ] Positive corpus added / updated.
+- [ ] Benign corpus added / updated.
+- [ ] Null control measured (vs unplugged **and** vs block-everything).
+- [ ] Confusion matrix regenerated (`make eval`) and committed under `eval/matrices/`.
+- [ ] The two numbers are in the PR description below.
+
+**The two numbers:** attacks blocked = `…`, legitimate traffic killed = `…`.

limes_guard-0.17.1/.github/workflows/ci.yml

@@ -0,0 +1,60 @@
+name: ci
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+concurrency:
+  group: ci-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  gate:
+    name: gate (ruff · mypy --strict · pytest) — py${{ matrix.python-version }}
+    runs-on: ubuntu-latest
+    strategy:
+      # Every supported Python reports for itself. One red must not hide the others.
+      fail-fast: false
+      matrix:
+        # These are exactly the `Programming Language :: Python` classifiers in
+        # pyproject.toml, and `requires-python = ">=3.12"` is the claim they witness.
+        # A version claimed and never run is a promise with no witness.
+        python-version: ["3.12", "3.13", "3.14"]
+    env:
+      # uv reads this for both `uv sync` and the `uv run` calls inside make gate,
+      # so the whole gate runs on the matrix version rather than on .python-version.
+      UV_PYTHON: ${{ matrix.python-version }}
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          # NOT the default depth 1. tests/unit/test_frontier.py compares today's
+          # bytes against the v0.1 commit, read out of git history — and a shallow
+          # checkout cannot produce it. With the default, that ratchet failed on
+          # every push from v0.1 to v0.8: 16 red runs, one green, on v0.1 itself
+          # where the comparison was trivially true. The gate was green locally the
+          # whole time, because a normal clone has the history.
+          fetch-depth: 0
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+
+      - name: Install the matrix Python
+        run: uv python install ${{ matrix.python-version }}
+
+      - name: Sync dependencies
+        run: uv sync
+
+      - name: Say which tree and which Python this gate judges
+        run: |
+          uv run python -VV
+          make tree
+
+      - name: Gate — ruff + ruff format --check + mypy --strict + pytest
+        run: make gate

limes_guard-0.17.1/.github/workflows/release.yml

@@ -0,0 +1,109 @@
+name: release
+
+# Publishing is deliberate: a tag, or a hand-pulled lever. Never a push to main.
+on:
+  push:
+    tags: ["v*"]
+  workflow_dispatch:
+    inputs:
+      target:
+        description: "where to publish"
+        required: true
+        default: testpypi
+        type: choice
+        options: [testpypi, pypi]
+
+permissions:
+  contents: read
+
+jobs:
+  # The gate runs again here, on the exact tag, rather than trusting that the
+  # commit was green when it landed: a tag can be moved, and the thing published
+  # must be the thing judged (ADR 0026 — a witness interrogates the thing).
+  gate:
+    name: gate before publishing — py${{ matrix.python-version }}
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.12", "3.13", "3.14"]
+    env:
+      UV_PYTHON: ${{ matrix.python-version }}
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0        # the frontier ratchet reads v0.1's bytes from history
+      - uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+      - run: uv python install ${{ matrix.python-version }}
+      - run: uv sync
+      - run: make gate
+
+  build:
+    name: build sdist + wheel
+    needs: gate
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - uses: astral-sh/setup-uv@v5
+
+      - name: Build
+        run: uv build
+
+      - name: The tag and the version must be the same number
+        if: startsWith(github.ref, 'refs/tags/v')
+        run: |
+          set -euo pipefail
+          tag="${GITHUB_REF_NAME#v}"
+          built="$(uv run --no-project --with tomli python -c \
+            'import tomli;print(tomli.load(open("pyproject.toml","rb"))["project"]["version"])')"
+          echo "tag=$tag  pyproject=$built"
+          # A tag that names a different version than the artifact it publishes is
+          # a release nobody can trace back: the sdist would claim one number and
+          # the git history another.
+          test "$tag" = "$built"
+
+      - name: Metadata must render on PyPI
+        run: uvx twine check --strict dist/*
+
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish-testpypi:
+    name: publish to TestPyPI
+    needs: build
+    if: github.event_name == 'workflow_dispatch' && inputs.target == 'testpypi'
+    runs-on: ubuntu-latest
+    environment: testpypi
+    permissions:
+      id-token: write          # Trusted Publishing (OIDC): no token on any machine
+    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/
+
+  publish-pypi:
+    name: publish to PyPI
+    needs: build
+    if: >-
+      startsWith(github.ref, 'refs/tags/v') ||
+      (github.event_name == 'workflow_dispatch' && inputs.target == 'pypi')
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write          # Trusted Publishing (OIDC): no token on any machine
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@release/v1

limes_guard-0.17.1/.gitignore

@@ -0,0 +1,18 @@
+# Python
+__pycache__/
+*.py[cod]
+*.egg-info/
+.venv/
+dist/
+build/
+
+# Tooling caches
+.mypy_cache/
+.ruff_cache/
+.pytest_cache/
+
+# OS
+.DS_Store
+
+# Eval scratch (the published matrices under eval/matrices/*.md ARE tracked)
+*.tmp

limes_guard-0.17.1/.gitleaks.toml

@@ -0,0 +1,42 @@
+# limes — secret-scanner configuration.
+#
+# limes is a package about credentials leaving a system, so its corpus and its
+# tests necessarily CONTAIN credential-shaped strings: that is the material under
+# test. A scanner reading them as leaks reports eleven findings on a repository
+# with no secret in it, and the cost of that noise is not zero — a reader who
+# learns to dismiss this scanner will dismiss it on the day it is right.
+#
+# So the exemptions are named one file at a time, with what each holds. They are
+# NOT a wildcard over tests/: a real key pasted into a new test must still ring.
+#
+# ADR 0010 already removed the worst of it — vendor key vectors are stored as
+# fragments the loader joins, so no contiguous credential literal sits in the
+# corpus. What remains below is what could not be assembled away: PEM headers,
+# a standard example JWT, and one obviously-fake key reused across four tests.
+#
+# Verify with: gitleaks detect --source . --redact -v
+
+title = "limes"
+
+[extend]
+useDefault = true
+
+[[allowlists]]
+description = """
+Synthetic detection material, verified: the base64 bodies decode to
+'EXAMPLE ONLY - not a key - synthetic' and 'PLACEHOLDER - synthetic - not a key',
+the JWT is the canonical example.com token (sub 1234567890, name Example), and
+the API key is the eight-character literal sk-live-AB12cd34. None is or ever was
+live. Each file is the input of a test that must find exactly these strings.
+"""
+paths = [
+  # The egress corpus: PEM headers and an example JWT the secrets detector must span.
+  '''^src/limes/corpus/egress/secrets_positive\.json$''',
+  # The secrets detector's own unit cases (the same PEM headers).
+  '''^tests/unit/egress/test_secrets_detector\.py$''',
+  # KEY = "sk-live-AB12cd34" — the payload the redaction tests mask and assert on.
+  '''^tests/unit/redaction/test_style\.py$''',
+  '''^tests/unit/mcp/test_redaction\.py$''',
+  '''^tests/integration/mcp/test_redaction_e2e\.py$''',
+  '''^tests/integration/mcp/test_http_e2e\.py$''',
+]

limes_guard-0.17.1/.pre-commit-config.yaml

@@ -0,0 +1,28 @@
+# limes pre-commit — the same checks make gate runs, at commit time.
+repos:
+  - repo: local
+    hooks:
+      - id: ruff-check
+        name: ruff check
+        entry: uv run ruff check --fix
+        language: system
+        types: [python]
+        pass_filenames: false
+      - id: ruff-format
+        name: ruff format
+        entry: uv run ruff format
+        language: system
+        types: [python]
+        pass_filenames: false
+      - id: mypy
+        name: mypy --strict
+        entry: uv run mypy
+        language: system
+        types: [python]
+        pass_filenames: false
+      - id: pytest
+        name: pytest
+        entry: uv run pytest -q
+        language: system
+        pass_filenames: false
+        stages: [pre-push]

limes_guard-0.17.1/.python-version

@@ -0,0 +1 @@
+3.12