Security Policy¶
Supported Versions¶
| Version | Supported | Status |
|---|---|---|
| 2.4.x | Yes | Current stable |
| < 2.4 | No | Older releases |
Reporting a Vulnerability¶
If you discover a security vulnerability in behave-lint, please report it responsibly:
- Do not open a public GitHub issue.
- Email security@paulenko.dev with a description of the vulnerability, steps to reproduce, and potential impact.
- You will receive an acknowledgment within 48 hours.
- We will investigate and provide a fix timeline within 7 days.
Security Architecture¶
behave-lint is a static analysis tool — it reads files and produces reports. It does not:
- Execute code
- Make network requests
- Import user-provided modules (except explicitly installed plugins)
- Use
evalorexec - Spawn subprocesses
Feature files are parsed with behave-model (read-only parsing, no
code execution). Step-definition rules analyze step text patterns only
— Python step definition files are never imported or executed.
Plugin Security¶
Plugins are Python packages installed via pip install. Users are
responsible for vetting plugins before installation. Plugin load
failures are isolated — a malicious or buggy plugin cannot crash the
core engine.