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 SPDX or CycloneDX, and the dependency graph as JSON or DOT. Open a dashboard, then go to Exports tab.
Every export is built in your browser from the analysis already loaded in the dashboard. So the file always 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 package in the graph, direct and transitive. Direct only keeps only the packages 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 packages score badly, and on which dimension. |
| Security | 11 | Which packages carry CVEs, how severe, and the version that fixes them. |
| Licenses | 5 | What license each package ships under, and where its source lives. |
| Everything | 45 | Everything the analysis measured. |
Every preset starts with Package and Release Found, so each row says which package it is and whether Deptools could resolve it.
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 vulnerabilities found on this version. |
| Critical CVEs | Number of vulnerabilities rated critical. |
| High CVEs | Number of vulnerabilities rated high. |
| Moderate CVEs | Number of vulnerabilities rated moderate. |
| Low CVEs | Number of vulnerabilities rated low. |
| CVE IDs | The identifiers of the vulnerabilities, CVE or GHSA, joined with /. |
| Fixed In | The version that fixes every known vulnerability of the package, the one the Fix 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 packages this package declares itself. |
| Transitive Dependencies | Number of packages 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. 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, then 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).
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.
Licenses are written as identifiers of the SPDX License
List, whatever the format. Deptools fixes their case
(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
list keeps its declared name and is never given an identifier it does not have.
SPDX 2.3, from the Linux Foundation, is the inventory format, for procurement, legal review and audits.
| Field | What Deptools writes |
|---|---|
spdxVersion, dataLicense | SPDX-2.3 and CC0-1.0. |
documentNamespace | A https://deptools.io/spdx/ URI made of your project name and a UUID generated for that file. |
creationInfo | The creation date, Deptools as the tool, and a comment giving the branch and the date of the analysis. |
packages[] | Your project first (SPDXRef-RootPackage, purpose APPLICATION), then one LIBRARY per package with its name, versionInfo, its repository as homepage, and its purl under externalRefs. |
downloadLocation | The release on its registry when the address is fixed (the npm tarball, the Maven Central directory of the version), otherwise the source repository, otherwise NOASSERTION. |
licenseDeclared | The license identifier, or the SPDX expression. A license not on the list is a LicenseRef-, described under hasExtractedLicensingInfos. 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). |
licenseConcluded, copyrightText | NOASSERTION. Deptools reads what the packages declare and does no legal review of its own. |
externalRefs | The purl, then one SECURITY advisory reference per CVE, pointing to its OSV page, with its severity and the fixed version in the comment. |
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, TEST_DEPENDENCY_OF, PROVIDED_DEPENDENCY_OF, DEV_DEPENDENCY_OF. |
A package that Deptools could not resolve keeps its entry, with a comment that
says so and gives the reason.
CycloneDX 1.5, from OWASP, is the security format, the one to give a vulnerability management tool such as Dependency-Track.
| Field | What Deptools writes |
|---|---|
bomFormat, specVersion, $schema | CycloneDX, 1.5, and the URL of the 1.5 JSON schema. |
serialNumber | urn:uuid: and a UUID generated for that file. |
metadata | The creation date, Deptools as the tool, your project as the described component with its repository, and the date, branch and build system of the analysis as properties. |
components[] | One library per package, with group, name, version, its purl, its licenses, the repository URL as a vcs external reference, and its scope: optional when only optional dependencies bring it in, required otherwise. |
properties | The Deptools scores of the package, deptools:score:overall then one per dimension. An unresolved package carries deptools:release-found set to false and the reason instead. |
licenses | One entry per declared license, by SPDX id or, off the list, by name. A single SPDX expression is written as an expression, and so is a single recent identifier the CycloneDX 1.5 schema does not list yet, such as Unicode-3.0. |
dependencies[] | One entry per package, an empty one included, plus one for your project holding your direct dependencies. |
vulnerabilities[] | One entry per vulnerability (CVE or GHSA), listing every package it affects: its OSV source, its severity (critical, high, medium, low), the CWE identifiers, its summary, its publication date, the affected version and, when a fix is released, the fixed version as unaffected. The key is absent when no CVE was found. |
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 the overall 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 |
| Vulnerability triage, by severity | CSV, preset Security |
| A license inventory for legal review | CSV, preset Licenses |
| An SBOM for procurement, an audit or a regulatory requirement | SPDX 2.3 |
| An SBOM for a security tool, CVEs included | CycloneDX 1.5 |
| 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.