<aside> <img src="/icons/list_blue.svg" alt="/icons/list_blue.svg" width="40px" />

Why .qll Contributions Are Necessary

Comparison of Sinks: When .qll Files Are Defined vs. Not Defined

Contributing to .qll

</aside>

Why .qll Contributions Are Necessary


It appears that, in the Python CodeQL queries, only the frameworks defined as QLL files under the python/ql/lib/semmle/python/frameworks/ directory are recognized as Sinks. For example, MarkupSafe is correctly detected as a Sink because it is defined in that location, whereas MarkUp is not detected due to the absence of a corresponding QLL definition. Given this, I would like to create a QLL file for MarkUp, write appropriate unit tests, and submit a pull request. Would it be possible to have the PR reviewed and potentially merged once submitted? I would greatly appreciate your guidance on this.

Best regards,

Kim Soo Hyun

Comparison of Sinks: When .qll Files Are Defined vs. Not Defined


Contributing to .qll