MineProductivity follows Semantic Versioning. Security fixes are provided for the latest released minor version. Older versions are supported on a best-effort basis until the next minor release supersedes them.
| Version | Supported |
|---|---|
Latest 2.x |
✅ |
1.11.x |
✅ (best-effort until 2.x adoption) |
| < 1.11 | ❌ |
Please do not open a public GitHub issue for security vulnerabilities.
Instead, report vulnerabilities privately via GitHub's private vulnerability reporting feature on this repository, or email the maintainers listed in CODEOWNERS.
Please include:
- A description of the vulnerability and its potential impact.
- Steps to reproduce, including affected package(s) under
src/mineproductivity/. - Any known mitigations.
- Acknowledgement within 5 business days.
- Investigation and severity assessment.
- Coordinated disclosure timeline agreed with the reporter.
- Patch release and public advisory once a fix is available.
MineProductivity is a pure-Python framework whose base install carries zero
third-party runtime dependencies; optional extras (events, connectors,
analytics, notebooks) pull in well-known scientific and I/O libraries only
when their features are used. The primary security surface is therefore:
- the framework's own code under
src/mineproductivity/(data ingestion viaconnectors, serialization, and plugin/entry-point discovery); - third-party plugins that implement the interface-only extension points (solver adapters, reasoning backends, renderers, connector adapters) — these run with the same trust as the host application and are outside this repository's control;
- the build/packaging toolchain and CI/CD configuration.
Dependency and static-analysis scanning (pip-audit, CodeQL, dependency
review) run in CI; see docs/governance/CI_CD_GUIDE.md
for the pipeline and any documented, time-boxed exceptions.