The version constraint == will introduce the risk of dependency conflicts because the scope of dependencies is too strict.
The version constraint No Upper Bound and * will introduce the risk of the missing API Error because the latest version of the dependencies may remove some APIs.
After further analysis, in this project,
The version constraint of dependency beautifulsoup4 can be changed to >=4.10.0,<=4.11.1.
The version constraint of dependency Jinja2 can be changed to >=2.7,<=3.1.2.
The version constraint of dependency paramiko can be changed to >=1.13.0,<=2.11.0.
The version constraint of dependency psutil can be changed to >=3.0.0,<=5.9.1.
The version constraint of dependency pymongo can be changed to >=2.4,<=4.1.1.
The version constraint of dependency python-nmap can be changed to >=0.3.4,<=0.7.1.
The version constraint of dependency redis can be changed to >=2.0.0,<=4.3.3.
The version constraint of dependency requests can be changed to >=2.4.0,<=2.15.1.
The version constraint of dependency urllib3 can be changed to >=1.9,<=1.26.9.
The version constraint of dependency validators can be changed to >=0.9,<=0.20.0.
The version constraint of dependency Werkzeug can be changed to >=0.6.1,<=2.1.2.
The above modification suggestions can reduce the dependency conflicts as much as possible,
and introduce the latest version as much as possible without calling Error in the projects.
The invocation of the current project includes all the following methods.
Hi, In nerve, inappropriate dependency versioning constraints can cause risks.
Below are the dependencies and version constraints that the project is using
The version constraint == will introduce the risk of dependency conflicts because the scope of dependencies is too strict. The version constraint No Upper Bound and * will introduce the risk of the missing API Error because the latest version of the dependencies may remove some APIs.
After further analysis, in this project, The version constraint of dependency beautifulsoup4 can be changed to >=4.10.0,<=4.11.1. The version constraint of dependency Jinja2 can be changed to >=2.7,<=3.1.2. The version constraint of dependency paramiko can be changed to >=1.13.0,<=2.11.0. The version constraint of dependency psutil can be changed to >=3.0.0,<=5.9.1. The version constraint of dependency pymongo can be changed to >=2.4,<=4.1.1. The version constraint of dependency python-nmap can be changed to >=0.3.4,<=0.7.1. The version constraint of dependency redis can be changed to >=2.0.0,<=4.3.3. The version constraint of dependency requests can be changed to >=2.4.0,<=2.15.1. The version constraint of dependency urllib3 can be changed to >=1.9,<=1.26.9. The version constraint of dependency validators can be changed to >=0.9,<=0.20.0. The version constraint of dependency Werkzeug can be changed to >=0.6.1,<=2.1.2.
The above modification suggestions can reduce the dependency conflicts as much as possible, and introduce the latest version as much as possible without calling Error in the projects.
The invocation of the current project includes all the following methods.
The calling methods from the beautifulsoup4
The calling methods from the Jinja2
The calling methods from the paramiko
The calling methods from the psutil
The calling methods from the pymongo
The calling methods from the python-nmap
The calling methods from the redis
The calling methods from the requests
The calling methods from the urllib3
The calling methods from the validators
The calling methods from the Werkzeug
The calling methods from the all methods
@developer Could please help me check this issue? May I pull a request to fix it? Thank you very much.