Skip to content

Security: CyberdyneCorp/CalculixPP

Security

SECURITY.md

Security Policy

CalculiX++ is a numerical finite-element solver. The most relevant risks are memory-safety issues (out-of-bounds access, use-after-free) reachable through the C++ API, the Python bindings, or the input-deck (.inp) / geometry import paths, and denial-of-service from untrusted input (e.g. a malformed deck or an extreme mesh/DOF count).

Supported versions

The project is pre-1.0 (0.x). Security fixes are applied to main and released in the next tag. There is no long-term-support branch yet.

Version Supported
main ✅
latest 0.x tag ✅
older tags ❌

Reporting a vulnerability

Please do not open a public issue for security vulnerabilities.

Report privately via GitHub's Report a vulnerability (Security → Advisories), or email the maintainer at leonardoaraujo.santos@gmail.com with:

  • a description of the issue and its impact,
  • steps or a minimal input that reproduces it (an .inp deck, a geometry file, or a code snippet driving the C++ / Python API),
  • affected version/commit.

We aim to acknowledge a report within a few days and to agree on a disclosure timeline with you. Please give us a reasonable window to ship a fix before any public disclosure.

Scope

In scope: the core library, the numerics layer, the input-deck parser, geometry import, and the Python bindings in this repo. Out of scope: vulnerabilities in third-party dependencies (report those upstream — NumPP, SciPP, CyberCadKernel, pybind11) and issues that require running deliberately hostile build tooling.

There aren't any published security advisories