Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.egisai.co/llms.txt

Use this file to discover all available pages before exploring further.

​
Versioning

egisai follows semantic versioning. The public surface of the package — anything documented on this site — is covered by the guarantee. Anything not documented (including modules whose names start with an underscore) is private and may change between releases without notice.
IncrementMeaning
MajorBackwards-incompatible change to the public API.
MinorBackwards-compatible feature additions.
PatchBackwards-compatible fixes.
Check your installed version with: 
import egisai
print(egisai.__version__)

​
Changelog

User-facing changes per release are recorded in CHANGELOG.md. We publish release notes for every tagged release on PyPI.

​
Verifying PyPI artifacts (optional)

Releases are published to PyPI via automation. To verify a wheel cryptographically using sigstore: 
pip download egisai==0.10.0 --no-deps
python -m sigstore verify identity \
  --cert-identity-regexp "https://github.com/EgisLabs/egisai-sdk/.+" \
  --cert-oidc-issuer "https://token.actions.githubusercontent.com" \
  egisai-0.10.0-py3-none-any.whl
Adjust the version to match the release you installed. A CycloneDX SBOM is attached to GitHub releases for supply-chain review.

​
Upgrading

pip install --upgrade "egisai[all]"
We recommend reading the changelog when crossing minor or major versions to catch behavior changes that might affect your application.

​
Yanking and security advisories

If a release is yanked or has an associated security advisory, you’ll find the notice on:
  • The PyPI page (yanked releases display prominently).
  • The repository’s GitHub Security Advisories tab.
  • SECURITY.md for general policy and reporting procedure.

​
What’s next

Installation

Pin the right version and verify your install.

Security

Privacy and security overview.