#Supported ecosystems and analysis methods

#Manifests

To find dependencies, CodeScoring primarily relies on parsing package manager manifest files. The platform supports parsing the following technologies:

The best result will be achieved by combining the main manifest file and the corresponding lock file, if provided by the package manager mechanism.

#PURL Types and Components

For unified dependency description, CodeScoring uses the Package URL (PURL) standard.

pkg:maven/org.apache.logging.log4j/log4j-core@2.17.2

When analyzing SBOM via the agent command or importing into the platform, CodeScoring recognizes and supports the following PURL types according to the specification:

Each component with a PURL is classified by type, which CodeScoring recognizes when importing SBOM files. The type is indicated in the type field within the component description.

{
  "components": [
    {
      "name": "log4j-core",
      "version": "2.17.2",
      "purl": "pkg:maven/org.apache.logging.log4j/log4j-core@2.17.2",
      "type": "library"
    }
  ]
}

Supported component types:

#System packages

As part of the OSA module, the platform supports analysing system packages of the following formats:

• Debian;
• Alpine;
• RPM;
• Astra Linux;
• ALT Linux;
• RED OS.

#Archive scanning

CodeScoring.OSA plugins support archive scanning in the following formats:

#Resolution mechanism in the absence of a lock file

If there is no lock file the system will try to resolve transitive OSS dependencies itself:

• Maven
  • for pom.xml and build.gradle format generation of maven-dependency-tree via the corresponding maven plugin
  • Maven version 3.8.8 and OpenJDK version 11 are used
• PyPi
  • generation of poetry.lock using the Poetry package manager
  • Python version 3.11.7 is used
• N.P.M.
  • generation of yarn.lock using the Yarn package manager
  • uses Node.js version 20.9.0
• Nuget
  • for csproj and sln format generation of project.assets.json using built-in nuget tools
  • uses .NET SDK version 8.0.404
• Packagist
  • generation of composer.lock using the Composer package manager
  • PHP version 8.2.26 is used
• Rubygems
  • generation of Gemfile.lock using the Bundler package manager
  • uses Ruby version 3.1.2p20

Generation of lock files by the system does not produce the best results in every case, since it often depends on the environment.

#Resolving dependencies in the build environment

Some package managers do not include transitive dependencies in their manifests by default. For high-quality compositional analysis when working with them, it is recommended to use a dependency resolution mechanism in the build environment.

When resolving dependencies in the environment, the agent checks for the absence of a lock file, independently launches the package manager or build tool, and generates a complete list of components taking into account the correct version of the build. The functionality is currently available for the following ecosystems:

• .NET
• Go
• Gradle
• Maven
• npm
• Poetry
• sbt
• yarn
• Conda

#Mechanism for searching dependencies using hashes

Search using hashes implies detection of direct inclusion of libraries in project's code. As part of this mechanism, all project files are hashed and these signatures are compared with known open source libraries.

Currently, hash searches occur for the following package manager indexes and the following file types:

• Maven
  • .jar
  • .war
  • .ear
• npm
  • .min.js
• PyPI
  • .whl
  • .egg
• Nuget
  • .nupkg

Hashes of files whose size does not exceed 512 bytes are not sent to the cloud.

#Build scanning for C and C++

If the Conan package manager and corresponding manifests are not used to build a C/C++ project, a special mode for analyzing the build process output can be used to get a list of used libraries.

In this mode, the Johnny console agent analyzes the build process using compiler flags and identifies the libraries used. Then, using the system cache, the location of the libraries and their source are determined.