Skip to content

Security: Extralit/extralit

Security

SECURITY.md

Security Policy

Supported versions

Security fixes land on the latest minor release and on develop. Older minor versions do not receive backported patches.

Release or branch Supported
0.6.x Yes
develop Yes
< 0.6 No

Reporting a vulnerability

Report privately. Do not open a public issue for a security problem.

Email contact@extralit.ai.

Include what you have: affected version or commit, reproduction steps, and the impact you believe it has. A partial report is more useful than no report.

What to expect

  • Acknowledgement within 5 business days.
  • An assessment within 15 business days, saying whether we consider it a vulnerability and what severity we assign.
  • Fix and disclosure coordinated with you. We will credit you in the published security advisory unless you ask us not to.

Extralit is maintained by a small team. These are the timelines we hold ourselves to, not a commercial SLA.

Scope

In scope: the Extralit server, Python SDK, and frontend in this repository.

The Hugging Face Spaces deployment bundle lives in the separate extralit-hf-space repository and is included here as a submodule. It is maintained by the same team, and reports about it are accepted at the address above.

Out of scope: vulnerabilities in upstream dependencies with no Extralit-specific exploit path (report those upstream), and findings against third-party instances of Extralit that you do not own or have permission to test.

Deploying Extralit safely

Extralit is self-hosted software that handles document data and user credentials. The default docker-compose.yaml is for local development, not production: change the default credentials, terminate TLS in front of the server, and do not expose Elasticsearch, PostgreSQL, or Redis to untrusted networks.

There aren't any published security advisories