Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Added a note to describe how to enable the PDO extension in the security analysis.
Reason
I spent a long time trying to understand why the SQLTaint errors were not showing for my project that uses PDO. I added the examples of SQL issues to my project but they still would still not be found despite other issues from the examples being found. Eventually after reading all the docs I found the answer that PDO must be enabled as an extension if it is not defined in composer.json as a dependency. Requiring PHP PDO as a dependency had not been done which I think is probably fairly common.
I thought this requirement could do with pointing out more prominently in the documentation and when describe the sinks involved in security analysis which i think is Psalms killer feature. After all the PDO sink is described on this page but users may not know it needs further configuration to enable it.
If you think it belongs somewhere else or could be worded better then happy to work on it. Hope you find this helpful and thanks for the project.