Wiki source code of Dependency Track

Version 31.1 by Milad Afshar-Jahanshahi on 2025/09/03 12:49

version	line-number	content
30.1	1	STILL UNDER CONSTRUCTION
	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
29.1	5	{{toc/}}
28.1	6
6.1	7	= Introduction =
	8
31.1	9	Dependency-Track is an open-source Software Composition Analysis (SCA) tool that helps organizations manage and secure their software supply chain. It automatically generates and maintains a Software Bill of Materials (SBOM) for projects, continuously monitoring dependencies for known vulnerabilities. In addition, it tracks license compliance of open-source components, giving teams greater visibility and control. By integrating seamlessly into DevOps and CI/CD pipelines, Dependency-Track makes it easier to embed security throughout the development lifecycle.
6.1	10
9.1	11	[[Vendor Page>>https://dependencytrack.org/]]
6.1	12
9.2	13	There are several useful resources available to get started with Deptrack:
6.1	14
9.2	15	[[Dependency-Track Documentation>>https://docs.dependencytrack.org/]]
6.1	16
14.1	17	[[Impact Analysis>>https://docs.dependencytrack.org/usage/impact-analysis/]]
	18
12.1	19	[[Collection-projects>>https://docs.dependencytrack.org/usage/collection-projects/]]
6.1	20
13.1	21	= Accessing Dependency-Track =
6.1	22
26.2	23	(% class="box warningmessage" %)
	24	(((
	25	Pilotkunden Preview ist
	26	)))
	27
13.1	28	== Preconditions in DevOps portal to access Dependency-Track ==
6.1	29
13.1	30	1. A Dependency-Track license must be assigned to the user
	31	1. Dependency-Track must be added to the tool list of the project
6.1	32
25.1	33	(% class="box warningmessage" %)
	34	(((
	35	⚠ Note
	36	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
	37	)))
	38
	39
	40
26.1	41
26.2	42
28.1	43
29.1	44
30.1	45
31.1	46
13.1	47	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	48
	49	== Via DevOps Portal ==
	50
16.1	51	Go to the DevOps Portal Homepage and click on the link //Project// in the Project Vulnerabilities tile:
6.1	52
15.2	53	[[image:deptrack.png\|\|alt="Deptrack -Tile" data-xwiki-image-style-border="true" height="211" width="459"]]
6.1	54
23.2	55	(% class="box warningmessage" %)
	56	(((
6.1	57	⚠ Note
16.2	58	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	59	\\[[image:login1.png\|\|alt="Untitled2.png" height="250" width="600"]]
23.2	60	)))
6.1	61
	62	== Via Direct URL ==
	63
13.1	64	You can also access Dependency-Track directly using the following link format:
23.1	65	[[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	66
	67	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.
	68
	69
26.1	70
	71	== Dependency-Track Jenkins Interaction ==
	72
	73	Nur sdcPipeline() wird unterstützt, nur maven (bisher), alles automatisch
	74
	75
26.2	76	== Collection Project und Unterprojekte ==
	77
27.1	78	TODO
	79
6.1	80	= Users, Projects and Roles =
	81
13.1	82	* 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	83
	84	⚠ Note
13.1	85	Projects in the DevOps portal are mapped to the corresponding subwikis in Dependency-Track.
6.1	86
13.1	87	* 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	88	** Role mapping: (((
	89	\|=Project Role in DevOps Portal\|=Permissions in XWiki
24.1	90	\|Admin\| POLICY_VIOLATION_ANALYSIS,''VIEW_POLICY_VIOLATION,''VIEW_PORTFOLIO,'VIEW_VULNERABILITY,''VULNERABILITY_ANALYSIS'
6.1	91	\|Master\|(% colspan="1" %)Can view, comment, and edit pages, but cannot delete content
	92	\|Developer\|(% colspan="1" %)Similar to Master
	93	\|Viewer\|Read-only access. Can only view content, no edits or comments allowed
	94
	95	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/]]
	96	)))
	97
	98	= Main Features =
	99
24.1	100	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	101
	102	== Collaborative Content Editing ==
	103
	104	* WYSIWYG and wiki syntax editors
	105	* Version control and history tracking
	106	* Inline and structured content editing
	107	* Commenting and annotations
	108
	109	== Advanced Page & Document Management ==
	110
	111	* Hierarchical page structure (nested pages)
	112	* Templates for creating structured documents
	113	* Tags, categories, and metadata support
	114	* File attachments and preview
	115
	116	== Powerful Search and Navigation ==
	117
	118	* Full-text search (Solr-based)
	119	* Faceted search filters
	120	* Page index, breadcrumbs, and navigation panels
	121
	122	== Macros and Widgets ==
	123
	124	* Built-in and custom macros (charts, galleries, diagrams)
	125	* Embedding of rich media (videos, iframes, etc.)
	126	* Markdown and LaTeX support
	127
	128
	129
	130

Wiki source code of Dependency Track

DevOps-as-a-Service