Wiki source code of Dependency Track

Version 26.1 by Milad Afshar-Jahanshahi on 2025/09/03 09:16

version	line-number	content
6.2	1	{{toc/}}
	2
8.1	3	[[image:logo-dependency-track.YzQAjtqS_Z2pMQkR.webp\|\|alt="Grafana Icon Logo PNG vector in SVG, PDF, AI, CDR format" data-xwiki-image-style-alignment="end" height="52" width="190"]]
6.1	4
	5	= Introduction =
	6
8.3	7	Dependency-Track is an open-source software composition analysis (SCA) tool. It creates and manages a software bill of materials (SBOM) for projects. The tool continuously checks dependencies for known vulnerabilities. It also tracks license compliance of open-source components. Teams gain visibility and control over their software supply chain. Helps integrate security into DevOps/CI-CD pipelines efficiently.
6.1	8
9.1	9	[[Vendor Page>>https://dependencytrack.org/]]
6.1	10
9.2	11	There are several useful resources available to get started with Deptrack:
6.1	12
9.2	13	[[Dependency-Track Documentation>>https://docs.dependencytrack.org/]]
6.1	14
14.1	15	[[Impact Analysis>>https://docs.dependencytrack.org/usage/impact-analysis/]]
	16
12.1	17	[[Collection-projects>>https://docs.dependencytrack.org/usage/collection-projects/]]
6.1	18
13.1	19	= Accessing Dependency-Track =
6.1	20
13.1	21	== Preconditions in DevOps portal to access Dependency-Track ==
6.1	22
13.1	23	1. A Dependency-Track license must be assigned to the user
	24	1. Dependency-Track must be added to the tool list of the project
6.1	25
25.1	26	(% class="box warningmessage" %)
	27	(((
	28	⚠ Note
	29	Im Gegensatz zu anderen Tools ist ein Login nur dann möglich, wenn der User eine Lizenz hat und in mindestens einem DepTrack Projekt eine Rolle hat
	30	)))
	31
	32
	33
26.1	34
13.1	35	After completing the preconditions, a project in Dependency-Track, which is part of the DevOps-as-a-Service toolchain, can be accessed via the DevOps Portal or directly through a URL.
6.1	36
	37	== Via DevOps Portal ==
	38
16.1	39	Go to the DevOps Portal Homepage and click on the link //Project// in the Project Vulnerabilities tile:
6.1	40
15.2	41	[[image:deptrack.png\|\|alt="Deptrack -Tile" data-xwiki-image-style-border="true" height="211" width="459"]]
6.1	42
23.2	43	(% class="box warningmessage" %)
	44	(((
6.1	45	⚠ Note
16.2	46	If you are still unable to access your project in Dependency-Track, it may be because you are logged in with an old session that still uses outdated permissions or To resolve this issue, please log out and then log in again:
18.1	47	\\[[image:login1.png\|\|alt="Untitled2.png" height="250" width="600"]]
23.2	48	)))
6.1	49
	50	== Via Direct URL ==
	51
13.1	52	You can also access Dependency-Track directly using the following link format:
23.1	53	[[https:~~/~~/deptrack-<customer~>.devops.t-systems.net/projects>>https://<customer>.devops.t-systems.net/xwiki/wiki/<pkey>/view]] where <customer> is the id of your DevOps-as-a-Service instance.
6.1	54
	55	If you are not already logged in to another tool in the toolchain or the DevOps portal, then you have to login using your configured SSO credentials.
	56
	57
26.1	58
	59	== Dependency-Track Jenkins Interaction ==
	60
	61	Nur sdcPipeline() wird unterstützt, nur maven (bisher), alles automatisch
	62
	63
6.1	64	= Users, Projects and Roles =
	65
13.1	66	* Projects, users and their roles in projects are managed in the DevOps Portal, the corresponding functions in Dependency-Track are disabled (UI and API)
6.1	67
	68	⚠ Note
13.1	69	Projects in the DevOps portal are mapped to the corresponding subwikis in Dependency-Track.
6.1	70
13.1	71	* When Dependency-Track is added as a tool to an existing or new project, a corresponding subwiki is automatically created. Users assigned to the project in the DevOps Portal are then added to the subwiki with the roles defined in the configuration :
6.1	72	** Role mapping: (((
	73	\|=Project Role in DevOps Portal\|=Permissions in XWiki
24.1	74	\|Admin\| POLICY_VIOLATION_ANALYSIS,''VIEW_POLICY_VIOLATION,''VIEW_PORTFOLIO,'VIEW_VULNERABILITY,''VULNERABILITY_ANALYSIS'
6.1	75	\|Master\|(% colspan="1" %)Can view, comment, and edit pages, but cannot delete content
	76	\|Developer\|(% colspan="1" %)Similar to Master
	77	\|Viewer\|Read-only access. Can only view content, no edits or comments allowed
	78
	79	A detailed description of the XWiki role model can be found [[here>>https://www.xwiki.org/xwiki/bin/view/Documentation/AdminGuide/Access%20Rights/Permission%20types/]]
	80	)))
	81
	82	= Main Features =
	83
24.1	84	Inside DevOps-as-a-Service, deptrack is mainly used for writing specifications and documentations. See below for a list of the main features of XWiki.
6.1	85
	86	== Collaborative Content Editing ==
	87
	88	* WYSIWYG and wiki syntax editors
	89	* Version control and history tracking
	90	* Inline and structured content editing
	91	* Commenting and annotations
	92
	93	== Advanced Page & Document Management ==
	94
	95	* Hierarchical page structure (nested pages)
	96	* Templates for creating structured documents
	97	* Tags, categories, and metadata support
	98	* File attachments and preview
	99
	100	== Powerful Search and Navigation ==
	101
	102	* Full-text search (Solr-based)
	103	* Faceted search filters
	104	* Page index, breadcrumbs, and navigation panels
	105
	106	== Macros and Widgets ==
	107
	108	* Built-in and custom macros (charts, galleries, diagrams)
	109	* Embedding of rich media (videos, iframes, etc.)
	110	* Markdown and LaTeX support
	111
	112
	113
	114

Wiki source code of Dependency Track

DevOps-as-a-Service