ankora 0.1.0__tar.gz

ankora-0.1.0/.github/actions/ankora-gate/action.yml

@@ -0,0 +1,34 @@
+name: "ankora gate"
+description: >
+  Replay your eval suite and fail the build if quality regressed against the
+  baseline. Provider API keys are read from the environment (pass them via
+  `env:` from repo secrets for real, non-deterministic replays).
+
+inputs:
+  config:
+    description: "Path to ankora.yaml"
+    required: false
+    default: "ankora.yaml"
+  working-directory:
+    description: "Directory to run ankora in"
+    required: false
+    default: "."
+  version:
+    description: "ankora version/spec to install with `uv tool install`"
+    required: false
+    default: "ankora"
+
+runs:
+  using: "composite"
+  steps:
+    - name: Install uv
+      uses: astral-sh/setup-uv@v5
+
+    - name: Install ankora
+      shell: bash
+      run: uv tool install "${{ inputs.version }}"
+
+    - name: Run ankora gate
+      shell: bash
+      working-directory: ${{ inputs.working-directory }}
+      run: ankora gate --config "${{ inputs.config }}"

ankora-0.1.0/.github/workflows/ankora.yml

@@ -0,0 +1,38 @@
+name: ankora
+
+# CI for the ankora project itself: lint, type-safe tests, and the keyless
+# end-to-end demo so `ankora gate` is exercised on every push and PR.
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.11", "3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Sync dependencies
+        run: uv sync
+
+      - name: Lint (ruff)
+        run: |
+          uv run ruff check
+          uv run ruff format --check
+
+      - name: Test (pytest)
+        run: uv run pytest -q
+
+      - name: Keyless end-to-end demo (exercises `ankora gate`)
+        run: bash examples/run_demo.sh

ankora-0.1.0/.github/workflows/publish.yml

@@ -0,0 +1,49 @@
+name: publish
+
+# Publish ankora to PyPI when a GitHub Release is published, using PyPI
+# Trusted Publishing (OIDC). No API tokens are stored in this repository —
+# see RELEASING.md for the one-time PyPI setup.
+
+on:
+  release:
+    types: [published]
+
+permissions:
+  contents: read
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+
+      - name: Build sdist + wheel
+        run: uv build
+
+      - name: Upload dist artifact
+        uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    # The `pypi` environment scopes the OIDC trust and lets you add approvals.
+    environment:
+      name: pypi
+      url: https://pypi.org/project/ankora/
+    permissions:
+      id-token: write # required for Trusted Publishing (OIDC); no tokens needed
+    steps:
+      - name: Download dist artifact
+        uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

ankora-0.1.0/.gitignore

@@ -0,0 +1,26 @@
+# Python
+__pycache__/
+*.py[cod]
+*.egg-info/
+.eggs/
+build/
+dist/
+
+# uv / venv
+.venv/
+
+# tooling caches
+.pytest_cache/
+.ruff_cache/
+
+# ankora local state
+.ankora/
+claude.md
+
+# private (do not publish)
+CLAUDE.md
+project.md
+prompts.md
+.env
+.env.*
+.ankora/

ankora-0.1.0/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 ankora contributors
+
+   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.

ankora-0.1.0/NOTICE

@@ -0,0 +1,5 @@
+ankora
+Copyright 2026 ankora contributors
+
+This product is licensed under the Apache License, Version 2.0 (see the LICENSE
+file). This product includes software developed by the ankora contributors.

ankora-0.1.0/PKG-INFO

@@ -0,0 +1,234 @@
+Metadata-Version: 2.4
+Name: ankora
+Version: 0.1.0
+Summary: Local-first, CI-native regression testing for LLM and agent applications.
+Project-URL: Homepage, https://github.com/ankora/ankora
+Project-URL: Repository, https://github.com/ankora/ankora
+Author: ankora contributors
+License: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Keywords: ci,evaluation,genai,llm,otel,regression-testing
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Quality Assurance
+Classifier: Topic :: Software Development :: Testing
+Requires-Python: >=3.11
+Requires-Dist: anthropic>=0.30
+Requires-Dist: httpx>=0.27
+Requires-Dist: openai>=1.30
+Requires-Dist: pydantic>=2
+Requires-Dist: pyyaml>=6
+Requires-Dist: rich>=13
+Requires-Dist: typer>=0.12
+Description-Content-Type: text/markdown
+
+# ankora
+
+**Turn the traces you already capture into regression tests that fail your CI when quality silently drops.**
+
+Teams have observability but no tests. ~89% of teams run some form of LLM
+observability, but only ~52% run evals — and quality is the No. 1 blocker to
+shipping LLM features to production. So prompt tweaks, model-version bumps, and
+silent provider changes ship undetected until users complain.
+
+`ankora` closes that gap from the supply side: it replays the traces you
+already have as a deterministic regression suite, scores the outputs, and
+**exits non-zero when quality regresses** — so a GitHub Action can block the
+merge. Local-first, bring-your-own-keys, no account, no telemetry.
+
+---
+
+## 60-second quickstart (no API keys required)
+
+Install from source with [uv](https://docs.astral.sh/uv/):
+
+```bash
+git clone https://github.com/ankora/ankora
+cd ankora
+uv sync
+```
+
+> Coming once published to PyPI: `uv tool install ankora` (or `pip install ankora`).
+
+Now run the fully offline demo — it uses the built-in deterministic `echo`
+provider and deterministic scorers, so **no network and no keys**:
+
+```bash
+bash examples/run_demo.sh
+```
+
+You'll watch the full loop **run → baseline set → gate** and see the CI contract
+both ways: a **green gate (exit 0)** when the run matches the baseline, then a
+**red gate (exit 1)** after a Case is deliberately broken:
+
+```
+==> 3. Gate against the baseline (clean — expect exit 0)
+No regressions — gate passed.
+    clean gate exit code: 0
+...
+==> 5. Gate again (regression — expect non-zero exit)
+1 regression(s) detected — failing the gate.
+    broken gate exit code: 1
+```
+
+That's the whole idea: **a regression makes the command exit non-zero.**
+
+---
+
+## The core loop
+
+In your own repo, the loop is four commands. Point `target.provider` at
+`openai`/`anthropic` in `ankora.yaml` for real replays (keys come from your
+env, below), or keep the keyless `echo` provider to try it out.
+
+```bash
+# 0. Scaffold ankora.yaml + an evals/ directory
+ankora init
+
+# 1. Turn an OpenTelemetry GenAI or Langfuse trace export into regression Cases
+#    (format is auto-detected; force it with --format otel|langfuse)
+ankora ingest traces.json --out evals/
+
+# 2. Replay + score the suite; saves a run under .ankora/runs/
+ankora run
+
+# 3. Promote a good run to the baseline
+ankora baseline set <run_id>
+
+# 4. The CI entrypoint: replay, diff vs baseline, exit non-zero on regression
+ankora gate
+```
+
+Inspect any two runs read-only (never fails the build):
+
+```bash
+ankora diff <baseline_run_id> <current_run_id>
+```
+
+Every command has `--help`; `--config` points at a non-default `ankora.yaml`,
+`--target provider:model` overrides the target, and `--concurrency` bounds
+parallel replays.
+
+### Configuration (`ankora.yaml`)
+
+```yaml
+version: 1
+suites: ["evals/**/*.yaml"]
+target:
+  provider: openai          # openai | anthropic | echo (keyless, for demos/CI)
+  model: gpt-4o-mini
+providers:
+  openai: {api_key_env: OPENAI_API_KEY}      # keys read from env, never inlined
+scorers:
+  - type: exact             # deterministic, no key needed
+    threshold: 1.0
+  - type: regex
+    pattern: '"country"'
+  - type: json_schema
+    schema: {type: object, required: [city, country]}
+  - type: llm_judge         # needs a provider key
+    judge: {provider: openai, model: gpt-4o}
+    rubric: "Score 1 if factually consistent with the reference, else 0."
+    threshold: 0.7
+  - type: embedding_similarity
+    model: {provider: openai, model: text-embedding-3-small}
+    threshold: 0.85
+gate:
+  fail_on: regression       # "regression" (vs baseline) or "absolute" (vs thresholds)
+  baseline: .ankora/baseline.json
+```
+
+---
+
+## Wire it into CI
+
+Add a workflow to your repo that runs `ankora gate` on pull requests. Provider
+keys come from repo secrets — ankora reads them from the environment and
+**never sees or stores your tokens**.
+
+```yaml
+# .github/workflows/ankora.yml
+name: ankora
+on: pull_request
+jobs:
+  gate:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+      - run: uv tool install ankora      # once published to PyPI
+      - run: ankora gate
+        env:
+          OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
+          ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}
+```
+
+A composite action that wraps those steps ships at
+[`.github/actions/ankora-gate`](.github/actions/ankora-gate/action.yml).
+Commit `.ankora/baseline.json` (or promote a run with `ankora baseline set`)
+so CI has something to compare against.
+
+---
+
+## Why it's different
+
+- **Local-first & offline.** Runs on your laptop or a CI runner. No account, no
+  login, no hosted service — and **no telemetry, ever.**
+- **Bring-your-own-keys.** Replays use *your* provider keys from env vars. We
+  never carry token cost and never see your tokens.
+- **Neutral & framework-agnostic.** Reads open formats (OpenTelemetry GenAI
+  semantic conventions first). Your suite is plain YAML checked into your repo —
+  no lock-in to a framework, provider, or storage backend.
+- **It fails your CI.** The whole point: `ankora gate` exits non-zero on
+  regression, so a quality drop blocks the merge instead of reaching users.
+
+---
+
+## v1 scope — and what's next
+
+**Shipped in v1:**
+
+- `init` — scaffold `ankora.yaml` + `evals/`
+- `ingest` — OpenTelemetry GenAI **and Langfuse** traces → regression Cases (format auto-detected; override with `--format {otel,langfuse,auto}`)
+- `run` — deterministic replay + scoring, persisted runs
+- `diff` — per-case comparison of two runs
+- `gate` — replay + baseline diff + non-zero exit on regression (the CI entrypoint)
+- `baseline set` — promote a run to the baseline
+- Providers: `openai`, `anthropic`, and a keyless `echo` provider for demos/CI
+- Scorers: `exact`, `regex`, `json_schema` (deterministic), `embedding_similarity`, `llm_judge`
+
+**Coming next (not built yet — no false promises):**
+
+- A scheduled drift watch (`run` on a cron against a live endpoint)
+- Multi-step agent-trajectory record/replay with tool mocking
+
+v1 targets single-turn LLM replay; recorded tool calls are kept as reference
+data but not yet re-executed.
+
+---
+
+## Development
+
+```bash
+uv sync
+uv run pytest          # all provider calls are mocked; no live API calls
+uv run ruff check
+uv run ruff format --check
+```
+
+## Releasing
+
+Maintainers: see [RELEASING.md](RELEASING.md). Publishing to PyPI happens
+automatically when you cut a GitHub Release, via
+[Trusted Publishing](https://docs.pypi.org/trusted-publishers/) (OIDC — no API
+tokens stored in the repo).
+
+## License
+
+Apache-2.0 — see [LICENSE](LICENSE) and [NOTICE](NOTICE).