feat(core): comprehensive Evalium platform release, infrastructure doctor, and hardening

.env.example

@@ -11,7 +11,7 @@
 APP_ENV=development
 
 # Application Name
-APP_NAME=EvalForge API
+APP_NAME=Evalium API
 
 # Enable Debugging: Set to 'False' in production
 DEBUG=True
@@ -84,3 +84,19 @@ DEEPSEEK_API_KEY=
 COHERE_API_KEY=
 NVIDIA_API_KEY=
 OLLAMA_BASE_URL=http://localhost:11434
+
+# ------------------------------------------------------------------------------
+# Stripe SaaS Billing Configuration (Optional)
+# ------------------------------------------------------------------------------
+STRIPE_SECRET_KEY=
+STRIPE_WEBHOOK_SECRET=
+STRIPE_PUBLISHABLE_KEY=
+
+# ------------------------------------------------------------------------------
+# Google OAuth 2.0 / OpenID Connect Authentication
+# ------------------------------------------------------------------------------
+# Backend Google Client credentials
+GOOGLE_CLIENT_ID=
+GOOGLE_CLIENT_SECRET=
+GOOGLE_REDIRECT_URI=https://evalforge.onrender.com/api/v1/auth/google/callback
+FRONTEND_URL=https://eval-forge-sandy.vercel.app

.github/pull_request_template.md

@@ -1,3 +1,5 @@
+# Pull Request Template
+
 ## Description / Summary
 
 Provide a concise summary of the changes introduced in this Pull Request.

.github/workflows/ci.yml

@@ -5,7 +5,7 @@ permissions:
 
 on:
   push:
-    branches: [main, dev, 'codex/**']
+    branches: [main, dev, "codex/**"]
   pull_request:
     branches: [main, dev]
 
@@ -105,7 +105,7 @@ jobs:
           cache-dependency-path: frontend/package-lock.json
       - uses: actions/setup-python@v5
         with:
-          python-version: '3.12'
+          python-version: "3.12"
           cache: pip
           cache-dependency-path: backend/requirements.txt
       - run: pip install -r backend/requirements.txt

.gitignore

@@ -218,12 +218,19 @@ __marimo__/
 .streamlit/secrets.toml
 
 # EvalForge Test Artifacts
-backend/artifacts/
-backend/datasets/
-artifacts/
-datasets/
+/backend/artifacts/
+/backend/datasets/
+/artifacts/
+/datasets/
 
 # Local environments and browser validation artifacts
 .venv/
 frontend/test-results/
 frontend/playwright-report/
+.env
+.env.*
+!.env.example
+!**/.env.example
+*.db
+*.sqlite
+*.sqlite3

.java-version

@@ -0,0 +1 @@
+21

.markdownlint.yaml

@@ -0,0 +1,13 @@
+extends: markdownlint/style/prettier
+MD013: false
+MD024: false
+MD026: false
+MD029: false
+MD033: false
+MD034: false
+MD036: false
+MD040: false
+MD041: false
+MD045: false
+MD058: false
+MD060: false

.node-version

@@ -0,0 +1 @@
+22

.nvmrc

@@ -0,0 +1 @@
+22

.python-version

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

.trunk/trunk.yaml

@@ -28,6 +28,13 @@ lint:
     - linters: [checkov]
       paths:
         - "docker/**"
+    - linters: [bandit]
+      paths:
+        - "scripts/**"
+    - linters: [osv-scanner]
+      paths:
+        - "backend/requirements.txt"
+        - "backend/requirements.lock"
     - linters: [ALL]
       paths:
         - "**/__pyrefly_virtual__/**"
@@ -40,9 +47,7 @@ lint:
     - git-diff-check
     - grype@0.118.0
     - hadolint@2.15.1
-    - isort@9.0.1
     - markdownlint@0.49.1
-    - osv-scanner@2.5.1
     - oxipng@10.2.1
     - prettier@3.9.8
     - ruff@0.16.8

.vscode/settings.json

@@ -4,19 +4,27 @@
       "docker/grafana/provisioning/datasources/*.yml"
     ]
   },
-  "python.defaultInterpreterPath": "C:\\Users\\hardi\\AppData\\Local\\Programs\\Python\\Python313\\python.exe",
+  "python.defaultInterpreterPath": "${workspaceFolder}\\.venv\\Scripts\\python.exe",
   "python.analysis.extraPaths": [
-    "${workspaceFolder}/backend"
+    "${workspaceFolder}/backend",
+    "${workspaceFolder}/sdk/python",
+    "${workspaceFolder}/cli",
+    "${workspaceFolder}/.venv/Lib/site-packages"
   ],
   "python.autoComplete.extraPaths": [
-    "${workspaceFolder}/backend"
+    "${workspaceFolder}/backend",
+    "${workspaceFolder}/sdk/python",
+    "${workspaceFolder}/cli",
+    "${workspaceFolder}/.venv/Lib/site-packages"
   ],
   "pyrefly.extraSearchPaths": [
-    "${workspaceFolder}/backend"
-  ],
-  "python.analysis.include": [
-    "backend"
+    "${workspaceFolder}/backend",
+    "${workspaceFolder}/sdk/python",
+    "${workspaceFolder}/cli",
+    "${workspaceFolder}/.venv/Lib/site-packages"
   ],
+  "java.configuration.updateBuildConfiguration": "automatic",
+  "python.analysis.include": ["backend"],
   "python.analysis.exclude": [
     "**/__pyrefly_virtual__/**",
     "C:/__pyrefly_virtual__/**",
@@ -36,5 +44,6 @@
     "**/__pyrefly_virtual__/**": true,
     "C:/__pyrefly_virtual__/**": true,
     "c:/__pyrefly_virtual__/**": true
-  }
+  },
+  "css.lint.unknownAtRules": "ignore"
 }

CODE_OF_CONDUCT.md

@@ -36,7 +36,7 @@ This Code of Conduct applies within all community spaces (GitHub repositories, i
 
 ## Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at `coc@evalforge.dev`. All complaints will be reviewed and investigated promptly and fairly.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at `coc@evalium.dev`. All complaints will be reviewed and investigated promptly and fairly.
 
 All community leaders are obligated to respect the privacy and security of the reporter of any incident.
 
@@ -66,4 +66,4 @@ Community leaders will follow these Community Impact Enforcement Guidelines in d
 
 ## Attribution
 
-This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 2.1, available at <https://www.contributor-covenant.org/version/2/1/code_of_conduct.html>.

CONTRIBUTING.md

@@ -1,6 +1,6 @@
-# Contributing to EvalForge 🚀
+# Contributing to Evalium 🚀
 
-Welcome to the **EvalForge** contributor community! We are thrilled to have you here. EvalForge is an open-source, production-grade evaluation platform designed to automate LLM testing, benchmarking, and quality assurance for AI engineering teams worldwide.
+Welcome to the **Evalium** contributor community! We are thrilled to have you here. Evalium is an open-source, production-grade evaluation platform designed to automate LLM testing, benchmarking, and quality assurance for AI engineering teams worldwide.
 
 Whether you are fixing a typo, adding a new LLM judge metric, writing tests, or improving UI components, your contributions are invaluable to shaping the future of AI engineering tools.
 
@@ -36,7 +36,7 @@ Whether you are fixing a typo, adding a new LLM judge metric, writing tests, or
 
 ## 1. Welcome Message
 
-EvalForge is maintained by developers, for developers. We foster an inclusive, welcoming, and collaborative environment. No contribution is too small! If this is your first time contributing to open source, we are here to support you step-by-step.
+Evalium is maintained by developers, for developers. We foster an inclusive, welcoming, and collaborative environment. No contribution is too small! If this is your first time contributing to open source, we are here to support you step-by-step.
 
 ---
 
@@ -53,10 +53,10 @@ Our vision is to build the definitive open-source infrastructure for LLM quality
 
 ## 3. Repository Architecture
 
-EvalForge is structured as a high-performance monorepo:
+Evalium is structured as a high-performance monorepo:
 
-```
-Eval-Forge/
+```text
+Evalium/
 ├── backend/                  # FastAPI 0.115+ Python backend gateway & services
 │   ├── app/
 │   │   ├── api/v1/          # RESTful routing endpoints & controllers
@@ -106,7 +106,7 @@ chmod +x scripts/setup-dev-env.sh
 
 ## 5. Environment Variables
 
-EvalForge uses strict environment variable validation via Pydantic (`BaseSettings`) and Vite `import.meta.env`.
+Evalium uses strict environment variable validation via Pydantic (`BaseSettings`) and Vite `import.meta.env`.
 
 Copy the sample environment files:
 
@@ -175,6 +175,7 @@ docker compose up --build
    ```
 
 2. **Start React Frontend:**
+
    ```bash
    cd frontend
    npm run dev
@@ -270,7 +271,7 @@ We use descriptive, prefix-based branch names:
 - `refactor/<short-description>`: Code refactoring
 - `test/<short-description>`: Adding or modifying test suites
 
-### Real Examples:
+### Real Examples
 
 - `feature/api-auth`
 - `feature/g-eval-engine`
@@ -286,7 +287,7 @@ Commits must follow the [Conventional Commits](https://www.conventionalcommits.o
 
 Format: `<type>(<scope>): <description>`
 
-### Standard Types:
+### Standard Types
 
 - `feat`: A new feature for the user or system
 - `fix`: A bug fix
@@ -297,7 +298,7 @@ Format: `<type>(<scope>): <description>`
 - `test`: Adding missing tests or correcting existing tests
 - `chore`: Updating build tasks, package manager configs, or dependencies
 
-### Examples:
+### Examples
 
 - `feat(eval): add DeepSeek-V3 LLM judge provider`
 - `fix(ws): resolve WebSocket reconnection exponential backoff memory leak`
@@ -336,7 +337,7 @@ Format: `<type>(<scope>): <description>`
 
 ## 15. Folder Organization
 
-```
+```text
 backend/app/
 ├── api/v1/endpoints/   # Single-responsibility route handlers
 ├── config/             # Environment & app configurations
@@ -384,19 +385,19 @@ backend/app/
 
 ## 20. Communication Channels
 
-Stay connected with the EvalForge core team and community:
+Stay connected with the Evalium core team and community:
 
-- **GitHub Discussions:** Ask questions, share ideas, and present RFC proposals in [GitHub Discussions](https://github.com/hardikkaurani/Eval-Forge/discussions).
-- **Issue Tracker:** Report verified bugs or suggest features via [GitHub Issues](https://github.com/hardikkaurani/Eval-Forge/issues).
-- **Security Inquiries:** Contact security maintainers privately via `security@evalforge.dev`.
+- **GitHub Discussions:** Ask questions, share ideas, and present RFC proposals in [GitHub Discussions](https://github.com/hardikkaurani/Evalium/discussions).
+- **Issue Tracker:** Report verified bugs or suggest features via [GitHub Issues](https://github.com/hardikkaurani/Evalium/issues).
+- **Security Inquiries:** Contact security maintainers privately via `security@evalium.dev`.
 
 ---
 
 ## 21. First Contribution Guide
 
 Looking for a place to start? Follow these steps:
 
-1. Browse issues tagged [`good first issue`](https://github.com/hardikkaurani/Eval-Forge/issues?q=is%3Aissue+is%3Aopen+label%3A"good+first+issue").
+1. Browse issues tagged [`good first issue`](https://github.com/hardikkaurani/Evalium/issues?q=is%3Aissue+is%3Aopen+label%3A"good+first+issue").
 2. Check out our catalog of 30 curated contributor tasks in [`docs/CONTRIBUTOR_ISSUES_CATALOG.md`](docs/CONTRIBUTOR_ISSUES_CATALOG.md).
 3. Comment on the issue to request assignment.
 4. Clone the repository and run `./scripts/setup-dev-env.sh` (or `.\scripts\setup-dev-env.ps1`).
@@ -442,7 +443,7 @@ git push origin fix/websocket-reconnect-badge
 
 We believe in celebrating our community! All contributors are recognized in:
 
-- The **EvalForge Leaderboard & README** section.
+- The **Evalium Leaderboard & README** section.
 - GitHub's native contributor graph.
 - Our quarterly **Release Notes** (`docs/RELEASE_NOTES_v1.0.0.md`).
 

GOVERNANCE.md

@@ -1,15 +1,15 @@
-# EvalForge Project Governance
+# Evalium Project Governance
 
-This document describes the governance structure, decision-making processes, and maintainer responsibilities for the **EvalForge** open-source project.
+This document describes the governance structure, decision-making processes, and maintainer responsibilities for the **Evalium** open-source project.
 
 ---
 
 ## 1. Governance Model
 
-EvalForge operates under a **Benevolent Meritocracy** model:
+Evalium operates under a **Benevolent Meritocracy** model:
 
 - **Merit-based Progression:** Anyone who contributes consistently to code, documentation, triage, or community support can progress to maintainer roles.
-- **Open Consensus:** Strategic architectural decisions, RFCs, and breaking API changes are discussed publicly in [GitHub Discussions](https://github.com/hardikkaurani/Eval-Forge/discussions) and issue threads.
+- **Open Consensus:** Strategic architectural decisions, RFCs, and breaking API changes are discussed publicly in [GitHub Discussions](https://github.com/hardikkaurani/Evalium/discussions) and issue threads.
 
 ---
 

MAINTAINERS.md

@@ -1,6 +1,6 @@
-# EvalForge Project Maintainers
+# Evalium Project Maintainers
 
-This document lists the core maintainers, triage leads, and security contacts for the **EvalForge** repository.
+This document lists the core maintainers, triage leads, and security contacts for the **Evalium** repository.
 
 ---
 
@@ -27,8 +27,8 @@ This document lists the core maintainers, triage leads, and security contacts fo
 
 For confidential security disclosures, contact:
 
-- **Email:** `security@evalforge.dev`
-- **Private Advisory:** [GitHub Security Advisories](https://github.com/hardikkaurani/Eval-Forge/security/advisories/new)
+- **Email:** `security@evalium.dev`
+- **Private Advisory:** [GitHub Security Advisories](https://github.com/hardikkaurani/Evalium/security/advisories/new)
 
 ---