As far as I can tell, projects and repositories are used pretty much interchangeably throughout most of the documentation. We develop a .NET micro services SaaS application and for simplicity’s sake, we have one repository for all of our backend services (projects are located in a sub path .\solution of the repo and referring scripts in a sub path .\build_scripts of the repo during CI).
Is there a way in Debricked to properly manage multiple projects within a single repository that I haven’t discovered yet? Scanning the repository finds all the dependencies and vulnerabilities of all projects, however exporting an SBOM for said repository results in an empty file (except for basic structure) and the “Overview” shows 0 vulnerabilities even though there are several.
Best answer by Benedita
View original