Security analysis tool for EVM bytecode. Supports smart contracts built for Ethereum, Hedera, Quorum, Vechain, Rootstock, Tron and other EVM-compatible blockchains.
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 coloredlogs can be changed to >=0.5,<=15.0.1.
The version constraint of dependency configparser can be changed to ==3.5.0b1.
The version constraint of dependency configparser can be changed to >=3.5.1,<=3.5.2.
The version constraint of dependency configparser can be changed to >=3.7.2,<=5.2.0.
The version constraint of dependency eth-utils can be changed to >=1.0.0b1,<=2.0.0.
The version constraint of dependency jinja2 can be changed to >=2.11.0,<=3.1.2.
The version constraint of dependency py-solc can be changed to >=0.6.0,<=3.2.0.
The version constraint of dependency requests can be changed to >=0.14.2,<=2.24.0.
The version constraint of dependency requests can be changed to ==2.26.0.
The version constraint of dependency z3-solver can be changed to >=4.8.11.0,<=4.11.2.0.
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 mythril, 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 coloredlogs can be changed to >=0.5,<=15.0.1. The version constraint of dependency configparser can be changed to ==3.5.0b1. The version constraint of dependency configparser can be changed to >=3.5.1,<=3.5.2. The version constraint of dependency configparser can be changed to >=3.7.2,<=5.2.0. The version constraint of dependency eth-utils can be changed to >=1.0.0b1,<=2.0.0. The version constraint of dependency jinja2 can be changed to >=2.11.0,<=3.1.2. The version constraint of dependency py-solc can be changed to >=0.6.0,<=3.2.0. The version constraint of dependency requests can be changed to >=0.14.2,<=2.24.0. The version constraint of dependency requests can be changed to ==2.26.0. The version constraint of dependency z3-solver can be changed to >=4.8.11.0,<=4.11.2.0.
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 coloredlogs
The calling methods from the configparser
The calling methods from the eth-utils
The calling methods from the jinja2
The calling methods from the py-solc
The calling methods from the requests
The calling methods from the z3-solver
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.