You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A repository may have requirements.txt with a templating engine which is being used to generate the final requirements.txt file.
For example, this is a line from the mentioned requirements.txt file:
Since we scan all requirements.txt files while doing a file system scan, we would be splitting the line by == to get the package name and version (as per logic here). It's better to add some validation against package names and versions, such as if the name doesn't use invalid characters, the version follows PEP440, etc.
Description
A repository may have
requirements.txt
with a templating engine which is being used to generate the finalrequirements.txt
file.For example, this is a line from the mentioned
requirements.txt
file:Since we scan all requirements.txt files while doing a file system scan, we would be splitting the line by
==
to get the package name and version (as per logic here). It's better to add some validation against package names and versions, such as if the name doesn't use invalid characters, the version follows PEP440, etc.Reference
aquasecurity/go-dep-parser#307
The text was updated successfully, but these errors were encountered: