Loading
Why are the dependencies declared in the Cargo.toml files, with their versions clearly specified, not detected by the tool Code insight ( Compliance Library (version 2.43_RC1)?

  • Aman Rajpoot (Flexera Software)

    Hi @Nafiseh​ ,

     

    Code Insight's Rust dependency analysis primarily relies on resolved dependency information (typically from Cargo.lock) to build an accurate dependency graph. While dependencies may be declared in Cargo.toml, this file often contains version ranges rather than the resolved versions that are required for dependency analysis.

    As a result, dependencies defined only in Cargo.toml may not always be identified during analysis. Providing a corresponding Cargo.lock file allows Code Insight to resolve and analyze the dependency tree more accurately.

    For further clarification or a deeper investigation specific to your project, please feel free to raise a support case with us, and we will be happy to assist.

    You can find more information on the supported ecosystems here:

    https://docs.codeinsight.revenera.com/user-guide/ref/automated-analysis/supported-development-ecosystems/supported-ecosystems/

    Expand Post

Loading
Why are the dependencies declared in the Cargo.toml files, with their versions clearly specified, not detected by the tool Code insight ( Compliance Library (version 2.43_RC1)?