Export reports and SBOMs
The Exports tab turns the analysis on screen into a file: a CSV report you configure column by column, a Software Bill of Materials (SBOM) in CycloneDX or SPDX, and the dependency graph as JSON or DOT. Open a dashboard, then go to the Exports tab.
The CSV report and the graph exports are built in your browser from the analysis loaded in the dashboard. Deptools builds the SBOM on its servers from that same analysis. Every file matches the analysis you are looking at, including an older one opened from the History tab of the project page.
Build a CSV audit report
The tab opens on three cards, one per kind of file: the spreadsheet report, the SBOM and the dependency graph. Each card says what its file holds. The CSV report is built in the card below them: the rows and the columns on the left, a preview of the file and its download on the right.


Rows
All dependencies exports every dependency in the graph, direct and transitive. Direct only keeps only the dependencies your build files declare. Each button carries its own count, so you know the size of the file before you build it.
Rows come in the same order in the file, the preview and the copied table: the direct dependencies first, then the transitive ones by depth, each level sorted by name.
This choice applies to the CSV alone. The SBOM and graph exports always carry the full graph, as their cards remind you.
Columns
Four presets fill the column selection for you. Scores is the selection you get the first time you open the tab.
| Preset | Columns | What it answers |
|---|---|---|
| Scores | 9 | Which dependencies score badly, and on which dimension. |
| Security | 11 | Which dependencies carry CVEs, how severe, and the version that fixes them. |
| Licenses | 5 | What license each dependency ships under, and where its source lives. |
| Everything | 45 | Everything the analysis measured. |
Every preset starts with Package and ends with Release Found, so each row says which package it is and whether Deptools could resolve it. Release Found is always the last column, whatever you pick.
A preset is a starting point, not a mode. Check or uncheck one box afterwards and the selection is yours, which the column count reports as a custom selection. Clear empties it. The dashboard remembers your rows and columns for each project, in your browser.
Preview and download
The preview shows the first five rows of the file, with the columns you picked, in the order of the file. Score cells are colored the way the dashboard colors them, zeros are faded and CVE counts take the colors of their severity, while the file holds the plain numbers. A score cell left empty reads empty in the preview, with the reason on hover: a package Deptools could not resolve, or a stable library without an activity score. The first column stays in place when you scroll the table sideways, and a counter on the right edge tells how many columns are out of view. The cross next to a column name removes that column. Copy for a spreadsheet puts the whole table, every row, on your clipboard, ready to paste into Google Sheets or Excel without a file.
The file name is built for you, in the form <project>-<preset>-<date>, with
-direct inserted before the date when the rows are Direct only. Edit it in
place if you need another one, or use the reset control to go back to the
generated name. The .csv extension is added for you.
The file name and the Download CSV button sit under the preview and stay in
view while you scroll through the columns. The button gives the number of rows
and columns of the file, and stays unavailable while no column is selected.
The spreadsheet card, at the top of the tab, shows the current selection (the
preset, the rows and the number of columns), and its Download button gives
the same file in one click.
The columns
The picker holds 45 columns in eight groups, in the order of the dashboard sidebar. Each group has its own checkbox, so you can select or clear a whole group in one click. Open a group to see each column with its short definition. The file always uses the order shown below, regardless of the order in which you select the columns.
The Group ID and Artifact ID columns are named after your ecosystem, in the picker and in the header of the file.
| Ecosystem | Group | Name |
|---|---|---|
| Maven, Gradle, sbt | Group ID | Artifact ID |
| npm | Scope | Name |
| Composer | Vendor | Name |
General
| Column | What it holds |
|---|---|
| Package | The package as your ecosystem writes it: group:artifact@version on Maven, Gradle and sbt, @scope/name@version or name@version on npm, vendor/package@version on Composer. |
| Package ID | The raw graph id, group:name:version, the id used in the graph JSON. An unscoped npm package writes _ in the group position. |
| Group ID, Scope or Vendor | Maven group, npm scope or Composer vendor. Empty for an unscoped npm package. |
| Artifact ID or Name | The package name on its own. |
| Version | The resolved version. |
| Depth in Graph | 1 for a package your build files declare, higher for a transitive one. |
| Brought In By | The packages that declare this one, as name@version, joined with /. Your project for a direct dependency. |
| Declared Scope | The scope the dependency is declared in (compile, runtime, optional…), every distinct one joined with /. |
| Repository URL | The source repository, empty when the analysis found none. |
| Release Found | true or false. |
| Not Found Reason | PACKAGE_UNKNOWN, VERSION_UNKNOWN, or UNSPECIFIED when the analysis marked the package without naming a cause. Empty for a package that resolved. |
| Maintenance Status | STABLE for a curated library that is complete on purpose, which explains an empty activity score. |
Scores. Overall Score, Security Score, Maintainability Score, Popularity Score, Activity Score and Community Score each hold that package's score from 0 to 10. The health score explains what goes into them.
Security
| Column | What it holds |
|---|---|
| Total CVEs | Number of CVEs found on this version. |
| Critical CVEs | Number of CVEs rated critical. |
| High CVEs | Number of CVEs rated high. |
| Moderate CVEs | Number of CVEs rated moderate. |
| Low CVEs | Number of CVEs rated low. |
| CVE IDs | The identifier of each CVE, as a CVE or GHSA id, joined with /. |
| Fixed In | The version that fixes every known CVE of the package, the one the Action plan recommends. (other artifact) follows it when the fix ships under another package name. |
Licenses
| Column | What it holds |
|---|---|
| License Name | Every license the package declares, joined with /, or Unknown. |
| License Type | permissive, weak copyleft, strong copyleft or unknown. For a package with multiple licenses, this is the most permissive one. |
Maintainability
| Column | What it holds |
|---|---|
| Latest Version | The latest release of the package. |
| Update Available | Major update, Minor update, Patch available or Up to date, as in the Maintainability tab. Empty when no latest release is known. |
| Outdated (days) | How far behind the latest release this version is, in days. |
| Missed Releases | How many versions behind the latest this version is. |
| Direct Dependencies | Number of dependencies this package declares itself. |
| Transitive Dependencies | Number of dependencies it pulls in below those. |
Popularity
| Column | What it holds |
|---|---|
| GitHub Stars | Number of stars on the source repository. |
| GitHub Watchers | Number of watchers on the source repository. |
| Library Dependents | Number of published releases of other packages that declare this package as a dependency, in any scope (test, provided, optional and development dependencies included). |
Activity
| Column | What it holds |
|---|---|
| Active Years | Number of years with at least one release, over the years counted in Years Measured. |
| Years Measured | Years the previous column is counted over: the last 5, or fewer for a package younger than that. |
| Commits (1 year) | Number of commits on the source repository over the last 12 months. |
| Versions (1 year) | Number of distinct versions of this package published over the last 12 months, not of the version on the row. |
| Last Commit Date | Date of the last commit, as YYYY-MM-DD. |
| Last Release Date | Date of the last release, as YYYY-MM-DD. |
Community
| Column | What it holds |
|---|---|
| Contributors | Number of unique contributors on the source repository. |
| Forks | Number of forks of the source repository. |
| Total Issues | Number of issues on the source repository, open and closed. |
Three things to know before you open the file:
- One row per package, direct dependencies first, and no row for your own project.
- The file includes a UTF-8 byte order mark, so Excel reads accents correctly.
- A package that Deptools could not resolve is exported with empty score cells and Release Found set to
false.
Export an SBOM
A Software Bill of Materials (SBOM) is an inventory of the software components shipped with your product. Customers, auditors, and regulators may ask you to provide one, and SBOMs are increasingly part of software security and compliance requirements.
In the EU, the Cyber Resilience Act (CRA) requires manufacturers to document the software components and dependencies in their products. An SBOM provides this information in a machine-readable form. Cyber Resilience Act, SBOM and BSI TR-03183-2 explains what the regulation and the German BSI guideline require, and which part of it this file covers. In the US, Executive Order 14028 helped establish SBOMs as part of federal software security requirements. The published minimum elements reference formats such as SPDX and CycloneDX. Exact requirements vary by regulation, agency, and contract.
Deptools exports the full dependency graph, not just the top-level dependencies.
Both files describe your project as their root element, which depends on your
direct dependencies, and on the runtime it needs when your build files declare
it. Then come one element per package and one relationship per edge of the
graph. Both files pass the official JSON schema of their format, and the SPDX
file passes the validator of the SPDX project (spdx-tools).
Neither file lists CVEs or Deptools scores. An SBOM describes one version of your
product, and that content stays true. The CVEs known for a version and the
scores change over time. For this reason, the German BSI technical guideline
TR-03183-2 forbids vulnerability information in an SBOM. A vulnerability
management tool such as Dependency-Track finds the CVEs itself from the purl
of each package. To share the CVEs or the scores as Deptools found them, export
the CSV report with the Security or Scores preset. The SBOM card
links to the Security preset for that reason.
Both files list the dependencies of the scopes your project analyzes, and say for each one whether your product ships it. A dependency provided by the environment, or used only to build and test, is listed and marked. See Dependencies your product does not ship.
Every package includes a purl in both formats, pkg:maven/group/artifact@version,
pkg:npm/name@version and pkg:npm/%40scope/name@version for a scoped package,
pkg:composer/vendor/package@version. That is the identifier most tools key on.
Your product gets a pkg:github purl when the project is linked to GitHub, and
none otherwise, see How the SBOM names your product.
The runtime gets none, see The runtime your product needs.
Licenses are written as identifiers of the SPDX License
List, whatever the format. A package often declares
its license by name, and Deptools matches that name to its identifier:
The Apache Software License, Version 2.0 becomes Apache-2.0. The Eclipse
Distribution License 1.0 becomes BSD-3-Clause, the identifier the Eclipse
Foundation gives it. Deptools fixes the case of an identifier
(CNRI-Python-GPL-Compatible) and replaces a deprecated identifier by its
current form (GPL-2.0 becomes GPL-2.0-only, GPL-2.0-with-classpath-exception
becomes GPL-2.0-only WITH Classpath-exception-2.0).
A license that is not on the SPDX list may still be one that Deptools
identifies by its identifier in the ScanCode
LicenseDB, such as
LicenseRef-scancode-indiana-extreme. Any other license gets a
LicenseRef-deptools- identifier built from its declared name. Every license is one the package declares, so CycloneDX marks it as
declared.
When a package declares a single license, or a single SPDX expression, and that
license is identified, the SBOM also gives it as the distribution license, the
license the package is distributed under: concluded in CycloneDX,
licenseConcluded in SPDX. Your product follows the same rule. An expression
with OR becomes the distribution license as written. The package is
distributed under either license, and choosing one is your call.
The SBOM gives no distribution license when the analysis has several licenses
for a package and no operator between them. A Maven POM lists its licenses
without saying whether they apply together or as a choice. The analysis also
records the expression of an npm dependency, such as MIT OR Apache-2.0, as
separate licenses. A package can also name several licenses without saying how
they combine, such as MIT & Apache 2.0: the SBOM lists each license. A
LicenseRef-scancode- license is identified, so it can be a distribution
license. A LicenseRef-deptools- license gives no distribution license, since
Deptools could not identify it. Deptools does no legal
review of its own: it writes a distribution license only when the declaration
leaves no doubt about it.
Hash of each package. The SBOM gives the SHA-512 of the file of each npm and Maven Central package. Deptools gets it the first time an analysis uses that version.
- npm. The hash the registry publishes for the tarball. An old version that the registry gives only a SHA-1 for gets no hash.
- Maven Central. The
.sha512file published beside the.jar. When there is none, Deptools computes the hash from the.jaritself. It downloads the.jaronly after the analysis, so a version that no analysis has used before may only get its hash at the next scan. - Composer. No hash. Packagist publishes none. The archive Composer installs is built from a commit when it is downloaded, so it is not the same file from one download to the next.
Packages from other Maven repositories, such as Google's, get no hash. Neither do the packages Deptools could not resolve, nor your product, whose file Deptools never sees.
Some Maven Central packages have no .jar, such as a Maven BOM, a POM that only
manages versions. Deptools finds this out when it tries to download the .jar,
after the analysis. Until then, the SBOM names a .jar that does not exist.
After that, the SBOM gives no file name and no file URI for the package.
CycloneDX 1.7, from OWASP, is the format the SBOM card recommends. It meets the format the BSI TR-03183-2 guideline asks for, CycloneDX 1.6 or later, and it is the one to give a vulnerability management tool such as Dependency-Track. Dependency-Track imports CycloneDX 1.7 from version 5.1.0, or 4.14.4 on the 4.x line. An older version refuses the file.
| Field | What Deptools writes |
|---|---|
bomFormat, specVersion, $schema | CycloneDX, 1.7, and the URL of the 1.7 JSON schema. |
serialNumber | urn:uuid: and a UUID generated for that file. |
metadata | The creation date. Deptools as manufacturer and as the tool, with the version of its SBOM generator. Your public contact in authors, once you set it. Your product as the described component, with the name, group, version, licenses and purl described in How the SBOM names your product, its repository, its manufacturer (the repository as url, then your public contact and the authors your build files name in contact), and the BSI properties of its file when Deptools can name that file. The date, branch, commit and build system of the analysis as properties (deptools:analysis:date, deptools:branch, deptools:commit, deptools:build-system), each one when known. |
components[] | One library per package, with group, name, version, its purl, its licenses, its external references, and its scope: excluded when it is not used at run time, optional when only optional dependencies bring it in, required otherwise. isExternal set to true when the environment provides it at run time. See Dependencies your product does not ship. Then one platform per runtime, see The runtime your product needs. |
manufacturer | The creator of the package, as a URL: its source repository, or its page on npm, Maven Central or Packagist when no repository is known. The analysis records no author email or name. Absent for a package that Deptools could not resolve and that declares no repository. For a runtime, the page of its project, such as https://www.php.net. |
externalReferences | The source repository twice, as vcs and as source-distribution, and the file of the release as distribution: the npm tarball, or the .jar on Maven Central. A reference Deptools does not know is left out. Packagist packages have no distribution, since the archive Composer installs depends on a commit the analysis does not record. A runtime has its source repository, as vcs and as source-distribution, such as https://github.com/php/php-src, and no distribution. The distribution reference holds the SHA-512 of its file in hashes when Deptools knows it. This is the place the mapping of BSI TR-03183-2 gives for the hash (Appendix, section 8.2). |
hashes | The same SHA-512, as SHA-512, on the package itself, the field CycloneDX defines for the hashes of a component. Absent when Deptools does not know the hash, see Hash of each package above. |
properties | The properties of the BSI TR-03183-2 taxonomy. bsi:component:filename is the name of the file in distribution, absent when that file is not known. bsi:component:executable, bsi:component:archive and bsi:component:structured are non-executable, archive and structured on every package: a .jar, an npm tarball and a Composer archive hold code and their own metadata, but the file itself does not run. An unresolved package also carries deptools:release-found set to false, and the reason in deptools:not-found-reason. A runtime carries none of the BSI properties, since it is not a file: it has deptools:version-constraint, and PHP also has deptools:php:extension and deptools:php:library. |
licenses | One entry per declared license, by SPDX id, each with acknowledgement set to declared. A single SPDX expression is written as an expression. A LicenseRef-scancode- or LicenseRef-deptools- identifier goes in name, alone or among several licenses, since CycloneDX accepts only listed identifiers in id. When the package declares a single identified license or expression, a second entry repeats it with acknowledgement set to concluded. A runtime has no licenses. |
dependencies[] | One entry per package, an empty one included, plus one for your project holding your direct dependencies and the runtimes. Each runtime has an empty entry. |
compositions[] | How complete each list in dependencies[] is. complete for a package Deptools resolved, since it read its manifest. unknown for a package it could not resolve. incomplete for a package that ships other packages inside its own archive, since those are not listed. Your project is incomplete when the analysis reports an error, such as a declared dependency it could not find or a build file it could not read, and complete otherwise. A runtime is unknown, since Deptools does not read what it depends on. |
SPDX 2.3, from the Linux Foundation, is the format for license review and procurement. The BSI TR-03183-2 guideline asks for SPDX 3.0.1 or later, which few tools read yet, so for that guideline give CycloneDX.
| Field | What Deptools writes |
|---|---|
spdxVersion, dataLicense | SPDX-2.3 and CC0-1.0. |
name, documentNamespace | The name of your product, as the SBOM names it, and a https://deptools.io/spdx/ URI made of that name and a UUID generated for that file. |
creationInfo | The creation date, Deptools as the tool, and a comment giving the branch, the commit and the date of the analysis. Your public contact as a second creator, Organization: <name> (<email>), when it has a name. |
packages[] | Your product first (SPDXRef-RootPackage, purpose APPLICATION), with its name, its version as versionInfo, its license, its file name, its first author with a name as originator (Person: <name> (<email>)) and its purl when they are known, see How the SBOM names your product. Then one LIBRARY per package with its name, versionInfo, its repository as homepage, and its purl under externalRefs. Then one OTHER per runtime, with its name, its minimum version as versionInfo, the page of its project as homepage, and a comment that gives the requirement, without externalRefs. |
downloadLocation | The file of the release on its registry when its address is fixed (the npm tarball, the .jar on Maven Central), otherwise the source repository, otherwise NOASSERTION. The source repository for a runtime, and for a Maven Central package without a .jar once Deptools has checked it. |
packageFileName | The name of that file, snakeyaml-1.33.jar or node-20.1.0.tgz. Absent when the file is not known. |
checksums | The SHA-512 of that file (SHA512), when Deptools knows it. |
licenseDeclared | The license identifier, or the SPDX expression. A license not on the list is a LicenseRef-scancode- or LicenseRef-deptools- identifier, described under hasExtractedLicensingInfos with its name. A package that declares several licenses gets NOASSERTION and a licenseComments that lists them: the analysis does not know whether they apply together (AND) or as a choice (OR). A runtime gets NOASSERTION. |
licenseConcluded | The same value as licenseDeclared when the package declares a single identified license or expression. NOASSERTION otherwise, and for a runtime. |
copyrightText | NOASSERTION. Deptools reads what the packages declare and does no legal review of its own. |
externalRefs | The purl. |
filesAnalyzed | false. The document describes packages, not the files inside them. |
relationships[] | DESCRIBES from the document to your project, then one relationship per edge, typed by its scope: DEPENDS_ON, or RUNTIME_DEPENDENCY_OF, OPTIONAL_DEPENDENCY_OF, PROVIDED_DEPENDENCY_OF, BUILD_DEPENDENCY_OF, TEST_DEPENDENCY_OF, DEV_DEPENDENCY_OF. A package or a project whose list of dependencies may be incomplete also gets DEPENDS_ON NOASSERTION, with the same rules as the CycloneDX compositions. Each runtime gets PROVIDED_DEPENDENCY_OF to your project, and DEPENDS_ON NOASSERTION. |
A package that Deptools could not resolve keeps its entry, with a comment that
says so and gives the reason.
How the SBOM names your product
The SBOM describes your product with what your build files declare. When they declare nothing for a field, the field is left out. Deptools takes these values from the build files at the root of the directory the project analyzes: the repository root, or the subfolder of a module.
| Build system | Name | Group | Version | License | Authors |
|---|---|---|---|---|---|
| Maven | artifactId | groupId, or the one of the parent POM | version, or the one of the parent POM | licenses, or the ones of a parent POM in your repository or of your own organization | developers, or the ones of a parent POM in your repository |
| Gradle | rootProject.name in the settings file, or the folder of a module | group | version | None | None |
| sbt | name, none for a module | organization | version, or version.sbt | licenses | None |
| npm | name, without its scope | the scope, such as @vue | version | license | author |
| Composer | the package of name | the vendor of name | version | license | authors |
Gradle reads group and version in the build script, then in
gradle.properties. A module of an sbt build declares its name in its own
settings, which Deptools does not read, so the SBOM names it after the
repository and the subfolder. Its group, version and licenses come only from
the settings scoped to ThisBuild. Maven resolves the properties of the POM and of its
parents. A value that still holds a property Deptools cannot resolve, such as a
${revision} your release sets on the command line, is left out. Deptools never
uses the license of the repository: only the license your build files declare
is written.
A parent POM downloaded from a registry gives its license only when it belongs
to your organization. Its groupId has to be the groupId your build files
declare, or a prefix of it: org.apache counts for org.apache.flink. The
groupId your build files declare is the one in your POM, or else the one in
the nearest parent POM of your repository. A groupId inherited from a
downloaded parent does not count. The license of a parent such as
spring-boot-starter-parent is the license of Spring Boot, not of your
product, so a project that declares none gets none.
An SPDX identifier or expression in your build files is kept, with its case and
deprecated forms fixed as for packages. Deptools does not match any other name
to an identifier, since the license is your choice. Such a name, for example
BSD 3-Clause License, gets a LicenseRef-deptools- identifier and no
distribution license. To have your license identified, write its SPDX
identifier in your build files, such as "license": "BSD-3-Clause" in
package.json.
Name. CycloneDX writes the group and the name apart, in group and name.
SPDX has no group field, so the name joins them: org.acme:app for Maven,
Gradle and sbt, @vue/runtime-core for npm, mexitek/phpcolors for Composer.
When your build files declare no name, the SBOM uses the repository and the
subfolder of the project, such as acme/platform/core, without a group. A CI
upload project has no repository, so its SBOM uses the project name as a last
resort.
Version. The version your pipeline declares comes first, then the version
your build files declare. A release often sets its version during the build,
and a branch usually declares a development version such as 2.4.1-SNAPSHOT.
Declare the version from your pipeline for the SBOM of a release.
purl. A project linked to GitHub gets pkg:github/<owner>/<repo>@<commit>,
followed by #<subfolder> for a module. A CI upload project gets none. Deptools
never writes a Maven, npm or Composer purl for your product: it cannot tell
whether that coordinate is published, nor whether the published package is
the one you scanned.
Licenses. Deptools normalizes them like the licenses of the packages. Composer reads
several licenses as a choice, so they become one OR expression when each one
is on the SPDX list. In every other case several licenses stay a list, and SPDX
writes NOASSERTION with the list in licenseComments.
Authors. The people your build files name as the authors of your product,
with their name and email address when given. An email that does not have the
form of an address is left out, and so is a value that still holds a property
Deptools cannot resolve. The authors are the contacts of your product's creator,
in metadata.component.manufacturer.contact after your
public contact, where BSI TR-03183-2 places the
creator's email. An author with the same email as your public contact is not
repeated. SPDX takes a single originator: the first author with a name, except
a name that contains a parenthesis, which a reader could take for the email.
Maven contributors and npm contributors and maintainers are not read, and
neither is the developers of a parent POM downloaded from a registry, such as
spring-boot-starter-parent: those are the authors of another project. The
SBOM may be shared outside your organization, so remove from your build files
any address you do not want published.
File name. Written only when the build tool names the file without
ambiguity: <artifactId>-<version>.jar, .war or .ear for Maven, and the
name npm pack gives, vue-runtime-core-3.5.45.tgz, for an npm package that
is not private. Nothing for any other Maven packaging, such as pom, and
nothing for Gradle, sbt and Composer. The
file name is also left out when the version in the SBOM is not the one your
build files declare, since it would then name another build. With the file
name, CycloneDX writes the BSI properties bsi:component:filename,
bsi:component:executable, bsi:component:archive and
bsi:component:structured, and SPDX writes packageFileName. The hash of that
file is never written: Deptools does not see the file you ship.
Dependencies your product does not ship
Your build files declare more than your product ships. Your application server provides some dependencies, and others only run when you build or test. The SBOM keeps them, and marks them so a reader can tell them apart from what you ship.
Deptools reads the scope each direct dependency is declared in. In CycloneDX, every package that only this dependency brings in gets the same marking. In SPDX, only the relationships from your project to its direct dependencies carry it. The relationships between two packages do not.
| Declared as | Meaning | CycloneDX | SPDX, from your project |
|---|---|---|---|
Maven and sbt compile, runtime and optional, Gradle implementation, api, runtimeOnly and optional, npm dependencies and optionalDependencies, Composer require | Shipped with your product | scope required, or optional when only optional dependencies bring it in | DEPENDS_ON, RUNTIME_DEPENDENCY_OF, OPTIONAL_DEPENDENCY_OF |
Maven and sbt provided, Gradle providedCompile and providedRuntime, npm peerDependencies | Provided at run time by the environment: your application server, your cluster, or the application that installs your package | isExternal set to true, with scope required, or optional for an optional peer dependency | PROVIDED_DEPENDENCY_OF |
Gradle compileOnly, test in Maven, Gradle and sbt, npm devDependencies, Composer require-dev | Not used at run time: compile time only, tests, development tooling | scope excluded | BUILD_DEPENDENCY_OF, TEST_DEPENDENCY_OF, DEV_DEPENDENCY_OF |
A package that a shipped dependency brings in is shipped, even when a
provided or a test dependency brings it in too. A package on the run time
classpath is in your product, whatever else uses it.
The SBOM lists only the scopes your project analyzes. The default selection
analyzes Gradle compileOnly and leaves out the test and development scopes. A
Gradle project with compileOnly dependencies therefore has excluded
packages, even with the default selection. You choose the scopes in
the dependency scopes.
The SBOM follows what your build files declare, not how your build packages
your product. Most packaging leaves provided dependencies out, a WAR or a
shaded JAR for example. The repackage goal of the Spring Boot Maven plugin
puts them in the executable JAR. Deptools does not run your build, so for that
JAR the SBOM marks as external packages that your JAR contains. Check how your
build packages provided dependencies before you deliver the SBOM.
The runtime your product needs
Your product runs on an interpreter or a virtual machine that the environment provides: PHP, Node.js, or a Java runtime. BSI TR-03183-2 asks for this runtime as a dependency, with the lowest version your product requires. The SBOM lists it when your build files declare it.
| Build system | What Deptools reads | Example |
|---|---|---|
| Composer | php, ext-* and lib-* in require | "php": "^8.2" gives PHP 8.2 |
| npm | engines.node in package.json | "node": ">=18.0.0" gives Node.js 18.0.0 |
| Maven | The Java version you compile for: <release> of the maven-compiler-plugin, then the maven.compiler.release property, <target> of the plugin, maven.compiler.target, and java.version | <java.version>17</java.version> gives OpenJRE 17 |
| Gradle | The Java version you compile for: options.release, then targetCompatibility, sourceCompatibility, the Kotlin jvmTarget, and the toolchain. Groovy and Kotlin build scripts alike | sourceCompatibility = JavaVersion.VERSION_1_8 gives OpenJRE 8 |
| sbt | Not read |
Version. The SBOM gives the lowest version that the requirement allows.
^7.2|^8.0 gives 7.2, and >=23.5.0 || ^22.13.0 || ^20.17.0 gives 20.17.0.
The requirement, as your build files write it, is kept in the
deptools:version-constraint property. A requirement that names no lowest
version, such as *, <9 or >8.1, gives no runtime at all. Deptools never
guesses a version.
Name. When any implementation would do, the guideline asks for the
standard one. The SBOM names PHP, Node.js, and OpenJRE for Java, which is the
name TR-03183-2 uses. The manufacturer of the runtime is the website of its
project, and its source is the repository of that project.
Java. Maven reads the parent POMs as well. A plugin configured in a profile
or in an execution is not read. Gradle reads the build script of the module,
then the allprojects and subprojects blocks of the root build script.
Convention plugins, in buildSrc or build-logic, are not read. An Android
build gets no Java runtime, since the app runs on Android and not on a Java
runtime.
In Maven as in Gradle, the first setting found in the order of the table
decides. When Deptools cannot read that setting, for example because it is a
variable, the SBOM gets no Java runtime. Deptools does not fall back on the
next setting, since that could write a version your build does not use. In
Gradle, two settings of the same kind with different versions also give no
Java runtime, for example two targetCompatibility lines set to 11 and 17.
PHP platform packages. The ext-* and lib-* platform packages of
require are not separate components. They are listed on the PHP component,
one deptools:php:extension or deptools:php:library property each, such as
ext-gd, or ext-intl ^1.0 when the requirement names versions. So they
appear only when php itself gives a version: with "php": "*", the SBOM has
no PHP component and lists none of them. The other platform packages are not
read: php-64bit, hhvm and the other variants of php, composer-plugin-api,
composer-runtime-api, and everything in require-dev.
In CycloneDX, the runtime is a platform with isExternal set to true and
scope required. It has no purl. With a purl, a vulnerability
management tool would report every CVE of PHP 8.2.0 for a requirement that
means PHP 8.2 or later. Check yourself the CVEs of the runtime version you
deploy. In SPDX, the runtime is a package with the purpose OTHER and a
PROVIDED_DEPENDENCY_OF relationship to your project.
Add your contact to the SBOM
Deptools generates the file, so every SBOM names Deptools as its creator. BSI TR-03183-2 also expects the entity responsible for the SBOM, which is you, preferably with an email address. Set a public contact for your organization, and every SBOM of its projects names it as well.
The contact is set in the Public contact card of the General tab of the organization settings. Only an owner or an admin can change it. It holds a name and an email address, and each one is optional:
- With both, the SBOM is the most complete.
- With an email address alone, CycloneDX carries the contact. SPDX requires a name, so the SPDX file leaves the contact out.
- With a name alone, both formats carry it, but nobody can reach it from the SBOM.
In CycloneDX, the contact goes in metadata.authors, as the creator of the
SBOM. Deptools stays in metadata.manufacturer. The contact also goes in
metadata.component.manufacturer.contact, as the contact of your product's
creator, before the authors your build files name.
A CI upload project has no repository, so its SBOM gives your product no other
creator than this contact and those authors. In SPDX, the contact is a second
creator, after the Deptools tool entry.
Anyone can download the SBOM of a project on a public repository, so the
contact of those projects is public. Use a role address, such as security@,
rather than a personal one.
One contact covers every project of the organization, and a project cannot have its own. A project that another entity publishes, such as a foundation, still gets the contact of the organization that holds it in Deptools.
The contact is added when you download the SBOM. A change applies to every SBOM downloaded afterwards, including the SBOMs of past scans. A file you already downloaded keeps the contact it was made with.
Until a contact is set, owners and admins see a reminder under the SBOM downloads of the Exports tab, and in the CI setup checklist of an upload project.
Get the SBOM without opening the dashboard
The same file is available in two other places, both built from the same analysis:
- From the scan history. The SBOM button of each row of the History tab downloads the SBOM of that scan, see Track scores over time.
- From your CI. A pipeline can download the SBOM of every scan it starts and
keep it with the build: with the
--sbomoption of the script for a project without GitHub, withsbom-formatin the GitHub Action, or withcurlfrom another CI.
Export the graph
Two more formats, for when you want the data rather than a report.
Graph JSON holds the nodes and edges the dashboard renders, unchanged. A node carries its id, version, depth, licenses, repository URL and one block per dimension with the raw metrics. An edge carries its source, its target, the version range that was declared, the version that was resolved, and the scope the dependency was declared in. The graph-level scores and the analysis errors are not in the file.
The payload holds one node your build files never declared, ROOT:ROOT:ROOT. It
stands for your project, and it is the source of one edge per direct dependency.
Skip that node and its edges in a script, or every count you compute includes a
package that does not exist.
Graphviz DOT renders in one command:
dot -Tsvg my-project-graph-2026-08-16.dot -o graph.svg
The graph reads from left to right. Your project is the first box, labeled with its name, with one arrow per direct dependency, so the whole file renders as a single tree. Each package box gives the readable name and version, then its package score, written as in the dashboard. A dashed arrow is an optional dependency. In an SVG render, hovering a box shows its score and its band.
The fill color follows the score bands:
| Fill | Band |
|---|---|
| Green | Excellent, 8.5 or above |
| Light green | Good, 7 or above |
| Yellow | Fair, 5 or above |
| Orange | Needs attention, 3 or above |
| Red | Critical, below 3 |
| Gray | No score, or a package Deptools could not resolve (its box says so) |
The first lines of the file repeat this legend as comments, with the project, the branch and the date of the analysis.
Which format for which need
| What you need | What to export |
|---|---|
| A spreadsheet to review with your team | CSV, preset Scores or Everything |
| CVE triage, by severity | CSV, preset Security |
| A license inventory for legal review | CSV, preset Licenses |
| An SBOM for a regulatory requirement (Cyber Resilience Act, BSI TR-03183-2) | CycloneDX 1.7 |
| An SBOM for a security tool such as Dependency-Track | CycloneDX 1.7 |
| An SBOM for procurement or a license review | SPDX 2.3 |
| The SBOM of every build, kept by your CI | CycloneDX 1.7, from your pipeline |
| Your own script | Graph JSON |
| A comparison between two scans | CSV, same scope and columns on both sides, or Graph JSON |
| A picture of the tree for a review or a slide | Graphviz DOT |
Next steps
- Try the demo to download each file before you connect a repository.
- The health score for what the score columns measure.
- Exclude dependency scopes since every export uses exactly the graph your scope selection produced.
- Add a README badge when one live number in the open is enough, and a file is more than you need.