Skip to content

Security: Kuhai9801/scieqlint

SECURITY.md

Security Policy

SciEqLint analyzes untrusted document text. Security is part of the product contract.

Supported versions

Security fixes are provided for the latest released minor version during v0.x. This policy should be revisited before v1.0.0.

Reporting a vulnerability

Do not open a public issue for a vulnerability. Use GitHub private vulnerability reporting or contact the maintainers listed in MAINTAINERS.md.

Please include:

  • affected version or commit,
  • operating system and Python version,
  • minimal reproduction,
  • expected behavior,
  • observed behavior,
  • whether arbitrary code execution, file read/write, denial of service, or data exposure is possible.

Runtime security contract

The checker runtime must not:

  • make network calls,
  • execute notebooks,
  • import user project modules,
  • evaluate Python code from documents,
  • run shell commands from the analysis core,
  • write files except explicit --output or init,
  • follow symlinks outside the project root by default,
  • read ignored files unless explicitly passed,
  • call SymPy text parsers on document content.

Dependency updates

Dependency updates should pass the normal CI loop. Security updates may be expedited, but they must not bypass tests that protect the runtime security contract.

There aren't any published security advisories