Metadata-Version: 2.4
Name: evalguard-sdk
Version: 2.0.0
Summary: DEPRECATED — install 'evalguardai' instead. Thin re-export shim kept so existing installs keep working; the canonical EvalGuard Python SDK is 'evalguardai' (mirrors npm @evalguard/sdk).
Author-email: EvalGuard <support@evalguard.ai>
License: Apache-2.0
Project-URL: Homepage, https://evalguard.ai/docs/install
Project-URL: Repository, https://github.com/EvalGuardAi/evalguard
Project-URL: Issues, https://github.com/EvalGuardAi/evalguard/issues
Keywords: deprecated,evalguard,evalguardai
Classifier: Development Status :: 7 - Inactive
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: Apache Software License
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3 :: Only
Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
Requires-Python: >=3.9
Description-Content-Type: text/markdown
Requires-Dist: evalguardai>=2.0.0

# evalguard-sdk (deprecation shim)

This package is a thin redirect. The canonical EvalGuard Python SDK is
**`evalguardai`** on PyPI.

```bash
pip install evalguardai
```

If you have `evalguard-sdk` already installed, it works — every import just
re-exports from the canonical `evalguard` module — but a `DeprecationWarning`
fires on first import. Switch your `requirements.txt` / `pyproject.toml` to
`evalguardai>=2.0.0` to silence it.

The reason both names exist: the npm side ships under the brand-only scope
`@evalguard/sdk`, and some Python users guess `evalguard-sdk` to mirror that.
This shim catches that case.

Docs: <https://evalguard.ai/docs/install>
