| Version | Supported |
|---|---|
| 2.x | ✅ Yes |
| < 2.0 | ❌ No |
Please do not open a public GitHub issue for security vulnerabilities.
Use one of the following channels:
- Private vulnerability report (preferred): Use the Report a vulnerability button on the Security tab. This keeps the report private until a fix is available.
- Email: Contact the maintainer directly at the address listed on the NCCU Schultz Lab GitHub profile.
A useful report includes:
- A description of the vulnerability and its potential impact
- Steps to reproduce (minimal example if possible)
- The version of Plottle affected
- Any suggested fix or mitigation
- Acknowledgement: within 5 business days
- Assessment and triage: within 2 weeks
- Fix or workaround: depends on severity; critical issues are prioritised
The following behaviors are intentional and documented — please do not report them as vulnerabilities unless you have found a bypass of the existing mitigations:
eval()in Analysis Tools and Data Tools: User-provided function expressions (e.g., custom curve-fit formulas) are evaluated witheval(). The execution context is restricted to a minimal namespace. This is acceptable for a local/classroom tool but should not be exposed to untrusted users on a public server without additional sandboxing.
This policy covers the plottle package and its Streamlit GUI and CLI. It does not
cover third-party dependencies — please report those to their respective maintainers.