Ask Me Anything sessions: A unique opportunity to learn more about Sigrid. Sign up now!

Publishing your dependencies to Sigrid’s Open Source Health

The Sigrid CI documentation contains instructions on how you can integrate Sigrid into your development platform, which allows you to publish your code to Sigrid after every change. That section of the documentation contains instructions for common development platforms, for example GitHub or Azure DevOps.

This page contains some additional instructions on how you can best publish your system’s open source libraries to Sigrid, so that they can be analyzed by Sigrid and shown in the Open Source Health page. The official, though somewhat obscure, term for this information is a SBOM (Software Bill of Materials).

First of all, it is not necessary to submit the binaries for every library. If your system uses a dependency management tool, it is usually sufficient to send the corresponding configuration files. For example, Maven uses pom.xml to list dependencies, Gradle uses build.gradle, and NPM uses package.json. If any of those files are included in your repository, they will be picked up automatically.

However, in some cases there might be extra options or caveats when using certain dependency management tools. The sections below contain some more specific instructions to take into consideration when using one of those dependency management tools. Also refer to supported dependency management tools and open source ecosystems for a complete list of all supported technologies.


Maven properties

Maven properties are supported. It is quite common to define library versions as Maven properties:


And then refer to those properties when the dependency is defined.


Sigrid understands these properties, and will resolve dependencies to the correct version. This also works if the property is defined in the top-level POM, and then used in the module POMs.

External parent POMs

Most Maven projects consist of multiple modules, which are then tied together by a “parent POM”, which is basically just a top-level pom.xml that contains shared configuration across the entire project.

In some cases, the parent POM itself also has a parent POM. This usually refers to a POM file which is shared across the entire organization, and tends to contain shared configuration across all projects in the organization. Having such an organization-wide used to be reasonably wide-spread, but is becoming increasingly rare as people move towards more independent repositories that do not have code dependencies on other repositories.

Sigrid is able to scan the parent POM, but only if the parent POM is included in the source code that was published. And that’s a problem, because as we just established these parent POMs are usually not part of the repository (by definition, as they contain all shared configuration across repositories). And if the parent POM is not published to Sigrid, then Sigrid is not able to read the file.

If you want Sigrid to scan your parent POM without having to include its original file in your upload, you can also generate a Maven dependency report and upload that to Sigrid. You can generate this report from the command line, as part of your build pipeline:

mvn dependency:tree > maven.tree

If Sigrid finds both POM files and the maven.tree file in your upload, the maven.tree file takes precedence.

Note that you need to run this command before you publish your code to Sigrid, otherwise the file will not end up in the upload. Also note that it is not necessary to commit this file to your repository, generating it on-the-fly in the pipeline is sufficient for Sigrid.


Unlike most other dependency management tools, Gradle does not use a configuration file format like XML or JSON or YAML. Instead, it uses a full-blown programming language (originally Groovy, but Kotlin build scripts are also supported in newer versions). Gradle build scripts are therefore incredibly flexible, but they are also much harder to analyze for tools like Sigrid.

If you use the configuration DSL to define your dependencies, Sigrid will automatically pick them up.

dependencies {
    api ""
    testImplementation "org.junit.jupiter:junit-jupiter:5.7.2"

Defining dependencies in this way will work just fine. However, there are much more flexible ways. You can define ext properties. You can define properties in You can have full-blown Groovy/Kotlin logic. If you project uses these dynamic features, Sigrid might not be able to pick up all dependencies (again, it’s hard to say where the line is exactly, since Gradle is so flexible).

However, Gradle also supports lockfiles. These lockfiles define exactly which libraries and version are used by your projects, and are committed to your repository. If your codebase contains a Gradle lockfile, Sigrid will use this lockfile instead of build.gradle. This ensures Sigrid is able to extract all of your project’s dependencies. Note that using a lockfile is a best practice even without considering Sigrid, as this allows for fully reproducible builds. Sigrid will only consider lockfiles when transitive scanning is set to true.


NPM dependencies are defined in package.json, but NPM also generates a lockfile called package-lock.json. Since the lockfile defines the exact versions, Sigrid will prioritize the lockfile over the regular package.json.


Yarn is very similar to NPM, but its lockfile is called yarn.lock instead of NPM’s package-lock.json. Like for NPM, Sigrid will prioritize the lockfile over package.json during its analysis.


Poetry is a Python dependency management tool, that is sometimes used as an alternative to the more popular PIP. Sigrid currently only supports analyzing the Poetry lockfile, which is called poetry.lock. This lockfile needs to be included in the codebase that is published to Sigrid, and is then analyzed automatically. Do note that using a Poetry lockfile is a best practice, so there are good reasons for using this lockfile even beyond Sigrid.

Other dependency management tools

This page provides some additional instructions and explanation for commonly used dependency management tools. For the complete list of all supportec technologies, refer to the supported dependency management tools and open source ecosystems.

Contact and support

Feel free to contact SIG’s support department for any questions or issues you may have after reading this document, or when using Sigrid or Sigrid CI. Users in Europe can also contact us by phone at +31 20 314 0953.