| Version | Supported |
|---|---|
| 0.1.x | Yes |
If you discover a security vulnerability in behave-priority, please report it responsibly.
Do not open a public GitHub issue.
Instead, email security@paulenko.dev with:
- A description of the vulnerability
- Steps to reproduce (minimal example)
- Potential impact
- Suggested fix (if any)
You will receive a response within 48 hours. If the vulnerability is confirmed, a fix will be released as soon as possible and you will be credited (unless you prefer to remain anonymous).
- Reorders scenario execution by parsing
@priority(N)tags fromscenario.tags - Uses
scenario.skip()to skip scenarios when fail-fast triggers - Modifies behave's runner feature list in-place during
before_all
- Does not execute arbitrary code from tags
- Does not modify files on disk
- Does not make network requests
- Does not access environment variables or secrets
Priority tags are parsed with strict regex validation. Invalid tags raise PriorityParseError — they never silently produce unexpected behavior.
PriorityQueue uses threading.Lock for thread-safe operations. The sorter and hooks are not designed for concurrent access to the same runner instance.