llm-evaluation-toolkit 0.1.0__tar.gz

llm_evaluation_toolkit-0.1.0/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,30 @@
+---
+name: Bug report
+about: バグの報告
+title: '[BUG] '
+labels: bug
+---
+
+## バグの説明
+<!-- 何が起きているか簡潔に説明してください -->
+
+## 再現手順
+1. 
+2. 
+3. 
+
+## 期待される動作
+<!-- 本来どう動くべきか -->
+
+## 実際の動作
+<!-- 実際に何が起きているか -->
+
+## 環境
+- OS: 
+- Python version: 
+- llm-evaluation-toolkit version: 
+
+## エラーメッセージ
+```
+エラーをここに貼り付け
+```

llm_evaluation_toolkit-0.1.0/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,15 @@
+---
+name: Feature request
+about: 新機能の提案
+title: '[FEAT] '
+labels: enhancement
+---
+
+## 解決したい問題
+<!-- どんな課題があるか -->
+
+## 提案する機能
+<!-- どんな機能があれば解決できるか -->
+
+## 代替案
+<!-- 他に考えられる解決方法があれば -->

llm_evaluation_toolkit-0.1.0/.github/pull_request_template.md

@@ -0,0 +1,15 @@
+## 変更内容
+<!-- このPRで何を変更したか -->
+
+## 変更の種類
+- [ ] バグ修正
+- [ ] 新機能
+- [ ] ドキュメント更新
+- [ ] リファクタリング
+
+## テスト
+- [ ] 既存のテストが全てパスする
+- [ ] 新しいテストを追加した
+
+## 関連Issue
+closes #

llm_evaluation_toolkit-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,41 @@
+name: CI
+
+on:
+  push:
+    branches: [ main, develop ]
+  pull_request:
+    branches: [ main ]
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.9", "3.10", "3.11"]
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install -e ".[dev]"
+
+      - name: Run linter
+        run: |
+          ruff check src/ tests/
+
+      - name: Run tests
+        run: |
+          pytest tests/ -v --cov=src/llm_eval --cov-report=xml --cov-fail-under=70
+
+      - name: Upload coverage report
+        uses: codecov/codecov-action@v4
+        with:
+          file: ./coverage.xml
+          fail_ci_if_error: false

llm_evaluation_toolkit-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,42 @@
+name: Release
+
+on:
+  push:
+    tags:
+      - "v*.*.*"
+
+jobs:
+  release:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+    env:
+      FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: true
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+
+      - name: Install build tools
+        run: |
+          python -m pip install --upgrade pip
+          pip install build twine
+
+      - name: Build package
+        run: python -m build
+
+      - name: Publish to PyPI
+        env:
+          TWINE_USERNAME: __token__
+          TWINE_PASSWORD: ${{ secrets.PYPI_API_TOKEN }}
+        run: twine upload dist/*
+
+      - name: Create GitHub Release
+        uses: softprops/action-gh-release@v2
+        with:
+          files: dist/*
+          generate_release_notes: true

llm_evaluation_toolkit-0.1.0/.gitignore

@@ -0,0 +1,234 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#   Usually these files are written by a python script from a template
+#   before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+# Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+# uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+# poetry.lock
+# poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+# pdm.lock
+# pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+# pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# Redis
+*.rdb
+*.aof
+*.pid
+
+# RabbitMQ
+mnesia/
+rabbitmq/
+rabbitmq-data/
+
+# ActiveMQ
+activemq-data/
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#   JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#   be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#   and can be added to the global gitignore or merged into this file.  For a more nuclear
+#   option (not recommended) you can uncomment the following to ignore the entire idea folder.
+# .idea/
+
+# Abstra
+#   Abstra is an AI-powered process automation framework.
+#   Ignore directories containing user credentials, local state, and settings.
+#   Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#   Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
+#   that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#   and can be added to the global gitignore or merged into this file. However, if you prefer, 
+#   you could uncomment the following to ignore the entire vscode folder
+# .vscode/
+# Temporary file for partial code execution
+tempCodeRunnerFile.py
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Streamlit
+.streamlit/secrets.toml
+
+# Virtual environment
+.venv/
+
+# Build artifacts
+dist/
+*.egg-info/
+
+# Coverage
+.coverage
+htmlcov/
+
+# Environment variables
+.env
+
+".venv_test/"

llm_evaluation_toolkit-0.1.0/CHANGELOG.md

@@ -0,0 +1,16 @@
+# Changelog
+
+All notable changes to this project will be documented here.
+
+## [0.1.0] - 2024-01-01
+
+### Added
+- `BLEUMetric` for translation and generation evaluation
+- `ROUGEMetric` for summarization evaluation  
+- `SemanticSimilarityMetric` using sentence-transformers
+- `LLMJudgeMetric` for reference-free evaluation
+- `OpenAIProvider` and `AnthropicProvider` for LLM integration
+- `DatasetLoader` with SQuAD and CNN/DailyMail support
+- `BaseEvaluator` for running multiple metrics at once
+- GitHub Actions CI/CD pipeline
+- Support for Python 3.9, 3.10, 3.11

llm_evaluation_toolkit-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,91 @@
+# llm-evaluation-toolkit への貢献ガイド
+# Contributing to llm-evaluation-toolkit
+
+貢献に興味を持っていただきありがとうございます！
+
+*Thank you for your interest in contributing!*
+
+---
+
+## はじめに / Getting Started
+
+1. リポジトリをフォークする / Fork the repository
+2. `develop` ブランチからフィーチャーブランチを作成する / Create a feature branch from `develop`
+```bash
+   git checkout develop
+   git checkout -b feat/your-feature-name
+```
+3. 変更を加える / Make your changes
+4. テストとリントを実行する / Run tests and linter
+```bash
+   ruff check src/ tests/
+   pytest tests/ -v --cov=src/llm_eval
+```
+5. コミットしてプッシュする / Commit and push
+```bash
+   git commit -m "feat: your feature description"
+   git push origin feat/your-feature-name
+```
+6. `develop` ブランチへのPull Requestを作成する / Open a Pull Request to `develop`
+
+---
+
+## 新しい評価指標を追加する / Adding a New Metric
+
+1. `src/llm_eval/metrics/your_metric.py` を作成する / Create `src/llm_eval/metrics/your_metric.py`
+2. `BaseMetric` を継承して `compute()` を実装する / Inherit from `BaseMetric` and implement `compute()`
+3. `src/llm_eval/metrics/__init__.py` からエクスポートする / Export from `src/llm_eval/metrics/__init__.py`
+4. `tests/test_metrics.py` にテストを追加する / Add tests in `tests/test_metrics.py`
+
+```python
+from __future__ import annotations
+
+from llm_eval.metrics.base import BaseMetric
+from llm_eval.types import EvalResult
+
+
+class YourMetric(BaseMetric):
+    def __init__(self):
+        super().__init__(name="your_metric")
+
+    def compute(
+        self,
+        predictions: list[str],
+        references: list[str],
+    ) -> EvalResult:
+        # ここに実装を書く / your implementation here
+        return EvalResult(metric_name=self.name, score=0.0)
+```
+
+---
+
+## コミットメッセージの形式 / Commit Message Format
+
+| プレフィックス / Prefix | 用途 / Usage |
+|------------------------|-------------|
+| `feat:` | 新機能 / New feature |
+| `fix:` | バグ修正 / Bug fix |
+| `test:` | テスト追加 / Adding tests |
+| `docs:` | ドキュメント更新 / Documentation |
+| `ci:` | CI/CD関連 / CI/CD changes |
+| `chore:` | メンテナンス / Maintenance |
+
+---
+
+## コードスタイル / Code Style
+
+このプロジェクトは `ruff` を使用しています。コミット前に必ず実行してください。
+
+*This project uses `ruff` for linting. Run before committing:*
+
+```bash
+ruff check src/ tests/
+```
+
+---
+
+## 質問・提案 / Questions & Suggestions
+
+バグ報告や機能提案は [Issues](https://github.com/swoswoyuu1156/llm-evaluation-toolkit/issues) からお気軽にどうぞ。
+
+*For bug reports and feature requests, feel free to open an [Issue](https://github.com/swoswoyuu1156/llm-evaluation-toolkit/issues).*

llm_evaluation_toolkit-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 swoswoyuu1156
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.