refactor: improve experimental source code pattern analysis of pypi packages #965
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
oracle-contributor-agreement
bot
added
the
OCA Verified
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request builds upon the work completed in #851, refactoring and refining the first step of source code analysis, matching suspicious code patterns. The intended behavior of this functionality is for the user to be able to specify pattern categories and subcategories (but no deeper) in a
.yamlfile, where this file path is provided indefaults.ini; a default file exists. These patterns will then be used to scan all python source code files for suspicious behavior. This suspicious pattern scanning will be the first phase of a broader feature for full source code analysis that includes dataflow analysis.