[{"data":1,"prerenderedAt":1200},["ShallowReactive",2],{"navigation_docs":3,"-core-concepts-cyber-resilience-act":129,"-core-concepts-cyber-resilience-act-surround":1195},[4,23,95,114],{"title":5,"path":6,"stem":7,"children":8},"Getting Started","\u002Fgetting-started","1.getting-started",[9,13,18],{"title":10,"path":6,"stem":11,"icon":12},"Getting started","1.getting-started\u002Findex","i-lucide-rocket",{"title":14,"path":15,"stem":16,"icon":17},"Try the demo","\u002Fgetting-started\u002Ftry-the-demo","1.getting-started\u002F1.try-the-demo","i-lucide-monitor-play",{"title":19,"path":20,"stem":21,"icon":22},"Quickstart","\u002Fgetting-started\u002Fquickstart","1.getting-started\u002F2.quickstart","i-lucide-play",{"title":24,"path":25,"stem":26,"children":27},"Guides","\u002Fguides","2.guides",[28,31,37,42,47,53,58,63,68,74,79,84,90],{"title":24,"path":25,"stem":29,"icon":30},"2.guides\u002Findex","i-lucide-map",{"title":32,"path":33,"stem":34,"icon":35,"group":36},"GitHub repository","\u002Fguides\u002Fconnect-a-github-repository","2.guides\u002F01.connect-a-github-repository","i-lucide-git-branch","Connect a project",{"title":38,"path":39,"stem":40,"icon":41,"group":36},"Without GitHub","\u002Fguides\u002Fanalyze-a-project-without-github","2.guides\u002F02.analyze-a-project-without-github","i-lucide-upload",{"title":43,"path":44,"stem":45,"icon":46,"group":36},"Dependency scopes","\u002Fguides\u002Fexclude-dependency-scopes","2.guides\u002F04.exclude-dependency-scopes","i-lucide-filter",{"title":48,"path":49,"stem":50,"icon":51,"group":52},"GitHub Actions","\u002Fguides\u002Fscan-from-github-actions","2.guides\u002F05.scan-from-github-actions","i-lucide-workflow","Automate",{"title":54,"path":55,"stem":56,"icon":57,"group":52},"Another CI","\u002Fguides\u002Fscan-from-another-ci","2.guides\u002F06.scan-from-another-ci","i-lucide-square-terminal",{"title":59,"path":60,"stem":61,"icon":62,"group":52},"Manage API keys","\u002Fguides\u002Fmanage-api-keys","2.guides\u002F07.manage-api-keys","i-lucide-key-round",{"title":64,"path":65,"stem":66,"icon":67,"group":52},"Many projects at once","\u002Fguides\u002Fcreate-many-projects-at-once","2.guides\u002F08.create-many-projects-at-once","i-lucide-layers",{"title":69,"path":70,"stem":71,"icon":72,"group":73},"Scores over time","\u002Fguides\u002Ftrack-scores-over-time","2.guides\u002F10.track-scores-over-time","i-lucide-trending-up","Act on the results",{"title":75,"path":76,"stem":77,"icon":78,"group":73},"Reports and SBOMs","\u002Fguides\u002Fexport-reports-and-sboms","2.guides\u002F11.export-reports-and-sboms","i-lucide-download",{"title":80,"path":81,"stem":82,"icon":83,"group":73},"README badge","\u002Fguides\u002Fadd-a-readme-badge","2.guides\u002F12.add-a-readme-badge","i-lucide-badge-check",{"title":85,"path":86,"stem":87,"icon":88,"group":89},"Organizations and plans","\u002Fguides\u002Forganizations-and-plans","2.guides\u002F13.organizations-and-plans","i-lucide-building-2","Organization and team",{"title":91,"path":92,"stem":93,"icon":94,"group":89},"Invite your team","\u002Fguides\u002Finvite-your-team","2.guides\u002F14.invite-your-team","i-lucide-users",{"title":96,"path":97,"stem":98,"children":99},"Core Concepts","\u002Fcore-concepts","3.core-concepts",[100,104,109],{"title":101,"path":97,"stem":102,"icon":103},"Core concepts","3.core-concepts\u002Findex","i-lucide-lightbulb",{"title":105,"path":106,"stem":107,"icon":108},"The health score","\u002Fcore-concepts\u002Fhealth-score","3.core-concepts\u002F1.health-score","i-lucide-gauge",{"title":110,"path":111,"stem":112,"icon":113},"Cyber Resilience Act","\u002Fcore-concepts\u002Fcyber-resilience-act","3.core-concepts\u002F7.cyber-resilience-act","i-lucide-landmark",{"title":115,"path":116,"stem":117,"children":118},"Reference","\u002Freference","5.reference",[119,122],{"title":115,"path":116,"stem":120,"icon":121},"5.reference\u002Findex","i-lucide-book-marked",{"title":123,"path":124,"stem":125,"children":126,"icon":128},"Ecosystems","\u002Freference\u002Fecosystems","5.reference\u002F1.ecosystems\u002Findex",[127],{"title":123,"path":124,"stem":125,"icon":128},"i-lucide-package",{"id":130,"title":131,"body":132,"description":1188,"extension":1189,"links":1190,"meta":1191,"navigation":1192,"path":111,"seo":1193,"stem":112,"__hash__":1194},"docs\u002F3.core-concepts\u002F7.cyber-resilience-act.md","Cyber Resilience Act, SBOM and BSI TR-03183-2",{"type":133,"value":134,"toc":1175},"minimark",[135,139,142,147,155,162,214,217,220,227,231,234,237,265,268,271,274,278,286,289,292,340,343,347,353,395,398,402,405,408,440,445,532,537,674,679,834,839,926,933,936,939,983,986,997,1000,1026,1030,1033,1043,1052,1058,1069,1073,1076,1088,1091,1113,1127,1131,1134],[136,137,138],"p",{},"The EU Cyber Resilience Act (CRA) makes a Software Bill of Materials (SBOM)\nmandatory for most products with digital elements sold in the European Union.\nThis page explains what the regulation requires about the components of your\nproduct, and what the German BSI guideline TR-03183-2 adds to it. It then maps\nthose requirements to the SBOM that Deptools produces, and lists what stays your\nresponsibility as a manufacturer.",[136,140,141],{},"This page describes the regulation and the guideline. It is not legal advice.\nThe official texts it relies on are listed at the end of the page, with the\narticles and sections used.",[143,144,146],"h2",{"id":145},"what-the-cyber-resilience-act-is","What the Cyber Resilience Act is",[136,148,149,150,154],{},"The Cyber Resilience Act is Regulation (EU) 2024\u002F2847. It sets cybersecurity\nrequirements for ",[151,152,153],"strong",{},"products with digital elements",", hardware and software, made\navailable on the EU market in the course of a commercial activity.",[136,156,157,158,161],{},"Most of its obligations fall on the ",[151,159,160],{},"manufacturer",": the company that develops\na product, or has it developed, and markets it under its own name or trademark.\nSelling it, monetizing it or giving it away free of charge makes no difference.",[163,164,165,178],"table",{},[166,167,168],"thead",{},[169,170,171,175],"tr",{},[172,173,174],"th",{},"Date",[172,176,177],{},"What applies",[179,180,181,190,198,206],"tbody",{},[169,182,183,187],{},[184,185,186],"td",{},"10 December 2024",[184,188,189],{},"The regulation enters into force",[169,191,192,195],{},[184,193,194],{},"11 June 2026",[184,196,197],{},"The rules on the notification of conformity assessment bodies (Chapter IV)",[169,199,200,203],{},[184,201,202],{},"11 September 2026",[184,204,205],{},"The reporting of actively exploited vulnerabilities and severe incidents (Article 14), for every product on the market, including those placed on it before 2027",[169,207,208,211],{},[184,209,210],{},"11 December 2027",[184,212,213],{},"Every other obligation, the SBOM included",[136,215,216],{},"The reporting obligation already applies. For an actively exploited\nvulnerability in your product, you send an early warning within 24 hours of\nbecoming aware of it, a notification within 72 hours, and a final report no\nlater than 14 days after a fix or a mitigation is available. A severe incident\nfollows the same first two deadlines, with a final report within one month. The\nreports go at the same time to the CSIRT designated as coordinator in your\nMember State and to ENISA, through the single reporting platform run by ENISA.",[136,218,219],{},"A failure to meet the essential requirements of Annex I, or the obligations of\nArticles 13 and 14, can be fined up to EUR 15 million or 2.5% of the worldwide\nannual turnover, whichever is higher.",[136,221,222,223,226],{},"Open source has its own rules. The regulation applies only in the course of a\ncommercial activity, and free and open source software that its manufacturer\ndoes not monetize is not one. An ",[151,224,225],{},"open-source software steward",", such as a\nfoundation that supports open source intended for commercial use, has lighter\nobligations: a documented cybersecurity policy and cooperation with the\nauthorities. It cannot be fined. A company that ships open source components\ninside its own product is the manufacturer of that product, whatever the\nlicenses of the components.",[143,228,230],{"id":229},"what-it-requires-for-the-components-of-your-product","What it requires for the components of your product",[136,232,233],{},"Annex I, Part II, point (1) requires the manufacturer to identify and document\nthe vulnerabilities and the components of the product, including by drawing up\nan SBOM. The SBOM must be in a commonly used, machine readable format, and cover\nat least the top-level dependencies of the product.",[136,235,236],{},"The regulation defines the SBOM as a formal record of the components of the\nsoftware and of the supply chain relationships between them (Article 3). Four\nmore rules shape what you do with it:",[238,239,240,247,253,259],"ul",{},[241,242,243,246],"li",{},[151,244,245],{},"The SBOM is part of the technical documentation"," (Annex VII). You keep it\nfor at least 10 years after the product is placed on the market, or for the\nsupport period if that is longer (Article 13(13)).",[241,248,249,252],{},[151,250,251],{},"A market surveillance authority can ask for it",", with a reasoned request\n(Annex VII, point 8).",[241,254,255,258],{},[151,256,257],{},"You do not have to publish it."," The regulation says so in recital 77. If\nyou choose to give it to your users, the user information says where to find\nit (Annex II, point 9).",[241,260,261,264],{},[151,262,263],{},"You remain responsible for the components you integrate."," Article 13(5)\nrequires due diligence on components sourced from third parties, free and\nopen source ones included.",[136,266,267],{},"Top-level dependencies are the minimum. In most projects the transitive\ndependencies far outnumber the direct ones, so an SBOM limited to direct\ndependencies leaves most of the packages you ship out of any vulnerability\ncheck.",[136,269,270],{},"The SBOM is the first of eight vulnerability handling requirements in the same\npart of Annex I. The other seven ask you to fix vulnerabilities without delay\nwith security updates, to test the security of the product regularly, to\ndisclose fixed vulnerabilities, to have a coordinated vulnerability disclosure\npolicy and a contact address for reports, and to distribute security updates\nsecurely, without delay and free of charge.",[136,272,273],{},"The regulation does not name an SBOM format. Article 13(24) allows the\nCommission to specify the format and the elements of the SBOM by an\nimplementing act.",[143,275,277],{"id":276},"where-bsi-tr-03183-2-fits","Where BSI TR-03183-2 fits",[136,279,280,281,285],{},"The German Federal Office for Information Security (BSI) publishes the\ntechnical guideline TR-03183, ",[282,283,284],"em",{},"Cyber Resilience Requirements for Manufacturers\nand Products",", to prepare manufacturers for the CRA. Part 2 covers the SBOM. Its\ncurrent version is 2.1.0, of 20 August 2025.",[136,287,288],{},"The guideline is not binding, and following it does not give a presumption of\nconformity with the CRA. The BSI states that harmonized European standards will\nreplace it as soon as they are available. Until then, it is the most detailed\npublic specification of what a CRA SBOM should contain, and a customer may make\nit a contractual requirement.",[136,290,291],{},"What Part 2 requires, in short:",[238,293,294,300,306,312,318,330],{},[241,295,296,299],{},[151,297,298],{},"Format."," JSON or XML, valid against CycloneDX 1.6 or later, or SPDX 3.0.1\nor later. Official releases of the specifications only.",[241,301,302,305],{},[151,303,304],{},"Depth."," Dependencies resolved recursively for every component in the scope\nof delivery, down to and including the first component outside that scope.\nThis goes far beyond the top-level minimum of the CRA.",[241,307,308,311],{},[151,309,310],{},"Source of the data."," The SBOM contains the information available during the\nbuild.",[241,313,314,317],{},[151,315,316],{},"One SBOM per version."," Each version of the software gets its own SBOM. A\nnew SBOM for the same version is issued only to add information or to fix an\nerror.",[241,319,320,323,324,329],{},[151,321,322],{},"No vulnerabilities."," The SBOM must not contain vulnerability information.\nA software version does not change, so its SBOM is static, while the\nvulnerabilities known for it change over time. They belong in a separate\nsecurity advisory, such as CSAF or VEX, see\n",[325,326,328],"a",{"href":327},"#where-the-cves-go","Where the CVEs go",".",[241,331,332,335,336,329],{},[151,333,334],{},"Data fields."," A required list for the SBOM itself and for each component,\nmapped to the Deptools file ",[325,337,339],{"href":338},"#what-the-deptools-sbom-covers","further down",[136,341,342],{},"SBOMs are generated with the most recent version of the guideline. The version\nbefore it remains accepted for six months after a new one is published, and an\nSBOM that complies when it is delivered stays compliant afterwards.",[143,344,346],{"id":345},"which-format-to-deliver","Which format to deliver",[136,348,349,350,329],{},"Deptools exports two formats. For the CRA and TR-03183-2, deliver\n",[151,351,352],{},"CycloneDX 1.7",[163,354,355,368],{},[166,356,357],{},[169,358,359,362,365],{},[172,360,361],{},"Format",[172,363,364],{},"Meets the TR-03183-2 format",[172,366,367],{},"Use it for",[179,369,370,382],{},[169,371,372,376,379],{},[184,373,374],{},[151,375,352],{},[184,377,378],{},"Yes, the guideline asks for 1.6 or later",[184,380,381],{},"The CRA, TR-03183-2, security tools such as Dependency-Track",[169,383,384,389,392],{},[184,385,386],{},[151,387,388],{},"SPDX 2.3",[184,390,391],{},"No, the guideline asks for SPDX 3.0.1 or later",[184,393,394],{},"License review and procurement, tools that do not read SPDX 3",[136,396,397],{},"Both formats are commonly used and machine readable, as the CRA asks. Only\nCycloneDX also meets the format rule of the guideline.",[143,399,401],{"id":400},"what-the-deptools-sbom-covers","What the Deptools SBOM covers",[136,403,404],{},"Deptools builds the SBOM from the analysis of your build files and lockfiles.\nIt lists the full dependency graph, direct and transitive, with one entry per\npackage and one relationship per dependency. The file passes the official JSON\nschema of its format, and contains no CVE and no score.",[136,406,407],{},"The tables below map each requirement of TR-03183-2 to the CycloneDX file:",[238,409,410,416,422,428,434],{},[241,411,412,415],{},[151,413,414],{},"Yes",": the field is in the file, on every package when it is a field of\neach package.",[241,417,418,421],{},[151,419,420],{},"Partly",": the field is in the file for some packages only, or holds only\npart of what the guideline asks.",[241,423,424,427],{},[151,425,426],{},"With your CI",": Deptools writes the field when your pipeline provides the\nvalue.",[241,429,430,433],{},[151,431,432],{},"With your settings",": the field holds what the guideline asks once you set\nits value in the settings of your organization.",[241,435,436,439],{},[151,437,438],{},"No",": the field is not in the file.",[136,441,442],{},[151,443,444],{},"The SBOM itself",[163,446,447,460],{},[166,448,449],{},[169,450,451,454,457],{},[172,452,453],{},"Requirement",[172,455,456],{},"In the file",[172,458,459],{},"Detail",[179,461,462,472,482,497,507,522],{},[169,463,464,467,469],{},[184,465,466],{},"Format and version",[184,468,414],{},[184,470,471],{},"CycloneDX 1.7, JSON",[169,473,474,477,479],{},[184,475,476],{},"No vulnerability information",[184,478,414],{},[184,480,481],{},"No CVE and no score, in either format",[169,483,484,487,489],{},[184,485,486],{},"Creator of the SBOM",[184,488,432],{},[184,490,491,492,496],{},"Deptools, by URL, in every file. The guideline expects the entity responsible for the SBOM, which is you, preferably with an email address. The ",[325,493,495],{"href":494},"\u002Fguides\u002Fexport-reports-and-sboms#add-your-contact-to-the-sbom","public contact"," of your organization provides it once you set it",[169,498,499,502,504],{},[184,500,501],{},"Timestamp",[184,503,414],{},[184,505,506],{},"The creation date, in UTC",[169,508,509,512,514],{},[184,510,511],{},"SBOM URI",[184,513,414],{},[184,515,516,517,521],{},"A ",[518,519,520],"code",{},"urn:uuid:"," serial number, unique to each file",[169,523,524,527,529],{},[184,525,526],{},"One SBOM per version",[184,528,426],{},[184,530,531],{},"Each analysis has its own SBOM, with the commit and the product version your pipeline declares. Your CI keeps one file per release",[136,533,534],{},[151,535,536],{},"The main component, your product",[163,538,539,549],{},[166,540,541],{},[169,542,543,545,547],{},[172,544,453],{},[172,546,456],{},[172,548,459],{},[179,550,551,561,575,597,610,644,664],{},[169,552,553,556,558],{},[184,554,555],{},"Name",[184,557,414],{},[184,559,560],{},"The name your build files declare, with its group. Otherwise the repository and subfolder of the project, or the project name for a CI upload project",[169,562,563,566,568],{},[184,564,565],{},"Version",[184,567,426],{},[184,569,570,571,574],{},"The product version declared by your pipeline. Otherwise the version your build files declare, often a development version such as ",[518,572,573],{},"2.4.1-SNAPSHOT"," on a branch",[169,576,577,580,582],{},[184,578,579],{},"Creator",[184,581,420],{},[184,583,584,585,588,589,592,593,596],{},"The repository of a project linked to GitHub, the public contact of your organization once you set it, and the authors your build files name (Maven ",[518,586,587],{},"developers",", npm ",[518,590,591],{},"author",", Composer ",[518,594,595],{},"authors","). A CI upload project has a creator only through that contact and those authors",[169,598,599,602,604],{},[184,600,601],{},"Other unique identifiers",[184,603,420],{},[184,605,516,606,609],{},[518,607,608],{},"pkg:github"," purl at the scanned commit, for a project linked to GitHub. None for a CI upload project, which has no public identifier to point to",[169,611,612,615,617],{},[184,613,614],{},"Licenses",[184,616,420],{},[184,618,619,620,623,624,627,628,631,632,635,636,639,640,643],{},"The licenses your build files declare: ",[518,621,622],{},"licenses"," in a POM or in ",[518,625,626],{},"build.sbt",", ",[518,629,630],{},"license"," in ",[518,633,634],{},"package.json"," or ",[518,637,638],{},"composer.json",". Deptools does not read the license of a Gradle project, and never uses the license of the repository. A name that is not an SPDX identifier gets a ",[518,641,642],{},"LicenseRef-deptools-"," identifier built from that name",[169,645,646,649,651],{},[184,647,648],{},"Filename, executable, archive and structured properties",[184,650,420],{},[184,652,653,654,627,657,635,660,663],{},"Deptools never sees the file you ship, so it writes the file name only where the build tool fixes it: a Maven ",[518,655,656],{},"jar",[518,658,659],{},"war",[518,661,662],{},"ear",", or an npm package that is not private, when the SBOM carries the version your build files declare. Absent for other Maven packagings, Gradle, sbt and Composer",[169,665,666,669,671],{},[184,667,668],{},"Hash value (SHA-512) of the deployable component",[184,670,438],{},[184,672,673],{},"Deptools never sees the file you ship",[136,675,676],{},[151,677,678],{},"Each dependency",[163,680,681,691],{},[166,682,683],{},[169,684,685,687,689],{},[172,686,453],{},[172,688,456],{},[172,690,459],{},[179,692,693,703,715,729,743,760,774,783,793,812,824],{},[169,694,695,698,700],{},[184,696,697],{},"Name and version",[184,699,414],{},[184,701,702],{},"As resolved by the analysis",[169,704,705,707,709],{},[184,706,601],{},[184,708,414],{},[184,710,516,711,714],{},[518,712,713],{},"purl"," on every package",[169,716,717,720,722],{},[184,718,719],{},"Dependencies, and their completeness",[184,721,414],{},[184,723,724,725,728],{},"The direct dependencies of each package, and a completeness statement for each list (",[518,726,727],{},"compositions",")",[169,730,731,734,736],{},[184,732,733],{},"Executable, archive and structured properties",[184,735,414],{},[184,737,738,739,742],{},"The properties of the BSI taxonomy. A ",[518,740,741],{},".jar",", an npm tarball or a Composer archive is a structured archive and does not run on its own",[169,744,745,748,750],{},[184,746,747],{},"Original licenses",[184,749,414],{},[184,751,752,753,756,757,759],{},"The licenses each package declares, marked as declared. A license outside the SPDX list gets its ScanCode LicenseDB identifier (",[518,754,755],{},"LicenseRef-scancode-",") when Deptools identifies it, a ",[518,758,642],{}," identifier otherwise",[169,761,762,765,767],{},[184,763,764],{},"Distribution licenses",[184,766,420],{},[184,768,769,770,773],{},"The declared license, when a package declares a single identified license or expression, ",[518,771,772],{},"OR"," included. Nothing when the analysis has several licenses and no operator between them: a Maven POM that lists several, an npm dependency whose expression the analysis records as separate licenses, or a package that names several licenses without saying how they combine. Nothing for a license Deptools could not identify",[169,775,776,778,780],{},[184,777,579],{},[184,779,420],{},[184,781,782],{},"The source repository, or the registry page of the package. Absent for an unresolved package that declares no repository",[169,784,785,788,790],{},[184,786,787],{},"Source code URI",[184,789,420],{},[184,791,792],{},"The source repository, not the exact tag or commit of the version",[169,794,795,798,800],{},[184,796,797],{},"Filename, and URI of the deployable form",[184,799,420],{},[184,801,802,803,805,806,808,809,811],{},"The npm tarball and the ",[518,804,741],{}," on Maven Central. Absent for Composer, for other Maven repositories and for unresolved packages. A Maven Central package without a ",[518,807,741],{},", such as a Maven BOM, names a ",[518,810,741],{}," that does not exist until Deptools checks it, after the analysis. After the check, it has none",[169,813,814,816,818],{},[184,815,668],{},[184,817,420],{},[184,819,820,821,823],{},"The SHA-512 of the npm tarball and of the ",[518,822,741],{}," on Maven Central. A Maven Central version may only get it at the next scan. None for an old npm version that has only a SHA-1, for other Maven repositories, for Composer and for unresolved packages. A Composer archive is not the same file from one download to the next",[169,825,826,829,831],{},[184,827,828],{},"Effective license (optional)",[184,830,438],{},[184,832,833],{},"Deptools does no legal review of its own",[136,835,836],{},[151,837,838],{},"Depth and source of the data",[163,840,841,851],{},[166,842,843],{},[169,844,845,847,849],{},[172,846,453],{},[172,848,456],{},[172,850,459],{},[179,852,853,863,873,895,916],{},[169,854,855,858,860],{},[184,856,857],{},"Recursive resolution",[184,859,414],{},[184,861,862],{},"The full transitive graph of the scopes your project analyzes",[169,864,865,868,870],{},[184,866,867],{},"Several versions of one package",[184,869,414],{},[184,871,872],{},"Each version is its own entry",[169,874,875,878,880],{},[184,876,877],{},"Scope of delivery",[184,879,414],{},[184,881,882,883,886,887,890,891],{},"Each package is marked from the scope its direct dependency is declared in: shipped, provided by the environment at run time (",[518,884,885],{},"isExternal","), or not used at run time (",[518,888,889],{},"excluded","). The marking follows your build files, not your packaging, see ",[325,892,894],{"href":893},"\u002Fguides\u002Fexport-reports-and-sboms#dependencies-your-product-does-not-ship","Dependencies your product does not ship",[169,896,897,900,902],{},[184,898,899],{},"Runtime and interpreter",[184,901,420],{},[184,903,904,905,907,908,911,912],{},"PHP, Node.js or OpenJRE, with the lowest version your build files require, provided by the environment (",[518,906,885],{},"). PHP platform packages are listed on the PHP component. Some projects get none, for example an sbt project, an Android build, or a requirement with no lowest version such as ",[518,909,910],{},"*",", see ",[325,913,915],{"href":914},"\u002Fguides\u002Fexport-reports-and-sboms#the-runtime-your-product-needs","The runtime your product needs",[169,917,918,921,923],{},[184,919,920],{},"Information available during the build",[184,922,420],{},[184,924,925],{},"Deptools reads your build files and does not run your build. With a lockfile, the graph matches what you install",[136,927,928,929,329],{},"This coverage changes as Deptools improves. The fields of the file are\ndescribed one by one in\n",[325,930,932],{"href":931},"\u002Fguides\u002Fexport-reports-and-sboms#export-an-sbom","Export reports and SBOMs",[143,934,328],{"id":935},"where-the-cves-go",[136,937,938],{},"The SBOM lists no CVE because the guideline forbids it, not because Deptools\nignores them. Every analysis checks each package of the graph, direct and\ntransitive, against the OSV database of known CVEs. The result is available in\nfour places:",[238,940,941,953,964,973],{},[241,942,943,946,947,950,951,329],{},[151,944,945],{},"The dashboard."," The ",[151,948,949],{},"Security"," tab lists the CVEs of every dependency,\nwith their severity and the version that fixes them. They set the Security\nscore of each package, see ",[325,952,105],{"href":106},[241,954,955,946,958,960,961,329],{},[151,956,957],{},"The CSV report.",[151,959,949],{}," preset exports, for each package, the\ncount of CVEs per severity, the identifier of each CVE and the version that\nfixes them all. See\n",[325,962,932],{"href":963},"\u002Fguides\u002Fexport-reports-and-sboms#build-a-csv-audit-report",[241,965,966,969,970,329],{},[151,967,968],{},"The Graph JSON."," Each package of the file carries its CVEs, for your own\nscripts. See\n",[325,971,932],{"href":972},"\u002Fguides\u002Fexport-reports-and-sboms#export-the-graph",[241,974,975,978,979,329],{},[151,976,977],{},"Your CI."," The status of a scan gives the count of CVEs per severity, and a\nquality gate can fail the build above a severity you choose. See\n",[325,980,982],{"href":981},"\u002Fguides\u002Fscan-from-github-actions#fail-the-build-on-quality-gates","Scan from GitHub Actions",[136,984,985],{},"These are the CVEs known on the day of the analysis. Scan again to check a\nversion against the CVEs published since.",[136,987,988,989,992,993,996],{},"A CVE in a dependency does not always mean your product is affected. Your code\nmay never call the vulnerable function, or may use the package in a way that\navoids the flaw. A ",[151,990,991],{},"VEX"," document (Vulnerability Exploitability eXchange)\nrecords that decision for each CVE: affected, not affected and why, fixed, or\nunder investigation. A ",[151,994,995],{},"CSAF"," document (Common Security Advisory Framework, an\nOASIS standard) is the advisory you publish for your users, and VEX is one of\nits profiles. TR-03183-2 gives both as examples of how to exchange\nvulnerability information.",[136,998,999],{},"Deptools does not produce VEX or CSAF documents. These open source tools do,\nfrom the SBOM that Deptools gives you:",[238,1001,1002,1014],{},[241,1003,1004,1007,1008,329],{},[151,1005,1006],{},"OWASP Dependency-Track"," imports a CycloneDX SBOM, matches its packages\nagainst vulnerability databases, lets you record an analysis decision for\neach finding, and exports those decisions as a CycloneDX VEX document. See\n",[325,1009,1013],{"href":1010,"rel":1011},"https:\u002F\u002Fdependencytrack.github.io\u002Fdocs\u002Fnext\u002Fguides\u002Fuser\u002Fexchanging-vex-documents\u002F",[1012],"nofollow","Exchanging VEX documents",[241,1015,1016,1019,1020,1025],{},[151,1017,1018],{},"Secvisogram",", an editor developed by the BSI, writes CSAF advisories in\nthe browser. The OASIS CSAF project lists it with the other\n",[325,1021,1024],{"href":1022,"rel":1023},"https:\u002F\u002Foasis-open.github.io\u002Fcsaf-documentation\u002Ftools.html",[1012],"CSAF open source tools",",\nsuch as validators and the software to publish your advisories.",[143,1027,1029],{"id":1028},"what-stays-your-responsibility","What stays your responsibility",[136,1031,1032],{},"An SBOM is one obligation among several. Deptools helps with some of the\nothers, and some are yours alone.",[136,1034,1035,1038,1039,1042],{},[151,1036,1037],{},"Components Deptools does not see."," Deptools reads the dependencies declared\nin the build files of the ",[325,1040,1041],{"href":124},"ecosystems it supports",".\nCode copied into your repository, native libraries, the operating system of a\ncontainer image and the dependencies of other ecosystems are not in its SBOM.\nIf your product ships them, your SBOM has to list them too.",[136,1044,1045,1048,1049,1051],{},[151,1046,1047],{},"Vulnerability handling."," The CRA requires you to handle the vulnerabilities\nof your product for its whole support period, at least five years in most cases.\nDeptools lists the CVEs of every dependency at every analysis, as described in\n",[325,1050,328],{"href":327},". Whether a CVE affects your product\ndepends on how your code uses the vulnerable package. That analysis is yours,\nand so are the VEX and CSAF documents that record it, the security updates and\nthe disclosure policy.",[136,1053,1054,1057],{},[151,1055,1056],{},"Reporting."," Reporting an actively exploited vulnerability or a severe\nincident to your CSIRT and to ENISA is the manufacturer's duty. No tool reports\nfor you.",[136,1059,1060,1063,1064,1068],{},[151,1061,1062],{},"Keeping the record."," The SBOM of every release belongs in your technical\ndocumentation for at least 10 years. Deptools keeps the completed analyses of a\nproject, as\n",[325,1065,1067],{"href":1066},"\u002Fguides\u002Ftrack-scores-over-time#read-the-scan-history","Track scores over time","\nexplains, but your own archive is the record the regulation asks for. Keep the\nfile your CI downloads with each release.",[143,1070,1072],{"id":1071},"keep-an-sbom-for-every-release","Keep an SBOM for every release",[136,1074,1075],{},"Each scan produces an analysis, and each analysis has its SBOM. To keep one SBOM\nper release:",[1077,1078,1079,1082,1085],"ol",{},[241,1080,1081],{},"Scan from your pipeline, on the build of each release.",[241,1083,1084],{},"Declare the product version, so the SBOM names your product with it. Each\nguide below explains how.",[241,1086,1087],{},"Keep the downloaded SBOM as an artifact of the build, then archive it with\nyour release.",[136,1089,1090],{},"The guides cover each pipeline:",[238,1092,1093,1100,1106],{},[241,1094,1095,1099],{},[325,1096,1098],{"href":1097},"\u002Fguides\u002Fanalyze-a-project-without-github#keep-the-sbom-of-every-build","Analyze a project without GitHub",",\nfor GitLab CI, Jenkins or any pipeline that pushes your build files.",[241,1101,1102,1105],{},[325,1103,982],{"href":1104},"\u002Fguides\u002Fscan-from-github-actions#download-the-sbom-of-every-scan",",\nfor a project linked to GitHub.",[241,1107,1108,1112],{},[325,1109,1111],{"href":1110},"\u002Fguides\u002Fscan-from-another-ci#download-the-sbom","Scan from another CI",", for a\nproject linked to GitHub, scanned from another pipeline.",[136,1114,1115,1116,1119,1120,1123,1124,329],{},"For a scan that already ran, the ",[151,1117,1118],{},"SBOM"," button of the ",[151,1121,1122],{},"History"," tab\ndownloads its SBOM, see\n",[325,1125,1067],{"href":1126},"\u002Fguides\u002Ftrack-scores-over-time#download-the-sbom-of-a-past-scan",[143,1128,1130],{"id":1129},"sources","Sources",[136,1132,1133],{},"Last reviewed in November 2026.",[238,1135,1136,1144,1152,1164],{},[241,1137,1138,1143],{},[325,1139,1142],{"href":1140,"rel":1141},"https:\u002F\u002Feur-lex.europa.eu\u002Feli\u002Freg\u002F2024\u002F2847\u002Foj\u002Feng",[1012],"Regulation (EU) 2024\u002F2847, the Cyber Resilience Act",",\non EUR-Lex. Articles 3, 13, 14, 24, 64, 69 and 71, Annexes I, II and VII,\nrecitals 18 and 77.",[241,1145,1146,1151],{},[325,1147,1150],{"href":1148,"rel":1149},"https:\u002F\u002Fwww.bsi.bund.de\u002FEN\u002FThemen\u002FUnternehmen-und-Organisationen\u002FStandards-und-Zertifizierung\u002FTechnische-Richtlinien\u002FTR-nach-Thema-sortiert\u002Ftr03183\u002FTR-03183_node.html",[1012],"BSI TR-03183, Cyber Resilience Requirements for Manufacturers and Products",",\non the BSI website. Part 2, version 2.1.0, sections 1, 3.1, 3.2, 4, 5 and 7.",[241,1153,1154,1159,1160,1163],{},[325,1155,1158],{"href":1156,"rel":1157},"https:\u002F\u002Fgithub.com\u002FBSI-Bund\u002Ftr-03183-cyclonedx-property-taxonomy",[1012],"The BSI CycloneDX property taxonomy",",\nfor the ",[518,1161,1162],{},"bsi:component:"," properties.",[241,1165,1166,1170,1171,329],{},[325,1167,1169],{"href":1010,"rel":1168},[1012],"Dependency-Track, Exchanging VEX documents",",\nand the ",[325,1172,1174],{"href":1022,"rel":1173},[1012],"OASIS list of CSAF open source tools",{"title":1176,"searchDepth":1177,"depth":1177,"links":1178},"",2,[1179,1180,1181,1182,1183,1184,1185,1186,1187],{"id":145,"depth":1177,"text":146},{"id":229,"depth":1177,"text":230},{"id":276,"depth":1177,"text":277},{"id":345,"depth":1177,"text":346},{"id":400,"depth":1177,"text":401},{"id":935,"depth":1177,"text":328},{"id":1028,"depth":1177,"text":1029},{"id":1071,"depth":1177,"text":1072},{"id":1129,"depth":1177,"text":1130},"What the EU Cyber Resilience Act requires about the components of your product, what the BSI TR-03183-2 guideline adds, and which part of it Deptools covers.","md",null,{},{"title":110,"icon":113},{"title":131,"description":1188},"fIgCbd8ebSgmJ8IHE3uXWqGTxDAlMzQnHAsQQBQkt0A",[1196,1198],{"title":105,"path":106,"stem":107,"description":1197,"icon":108,"children":-1},"What the 0 to 10 number measures, how it is computed for a package and for a project, and why it moves.",{"title":115,"path":116,"stem":120,"description":1199,"icon":121,"children":-1},"The ecosystems Deptools reads, and the build files it looks for in your repository.",1795209217869]