Wiki source code of Dependency Track

Version 26.2 by Milad Afshar-Jahanshahi on 2025/09/03 09:18

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
26.2	21	(% class="box warningmessage" %)
	22	(((
	23	Pilotkunden Preview ist
	24	)))
	25
13.1	26	== Preconditions in DevOps portal to access Dependency-Track ==
6.1	27
13.1	28	1. A Dependency-Track license must be assigned to the user
	29	1. Dependency-Track must be added to the tool list of the project
6.1	30
25.1	31	(% class="box warningmessage" %)
	32	(((
	33	⚠ Note
	34	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
	35	)))
	36
	37
	38
26.1	39
26.2	40
13.1	41	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	42
	43	== Via DevOps Portal ==
	44
16.1	45	Go to the DevOps Portal Homepage and click on the link //Project// in the Project Vulnerabilities tile:
6.1	46
15.2	47	[[image:deptrack.png\|\|alt="Deptrack -Tile" data-xwiki-image-style-border="true" height="211" width="459"]]
6.1	48
23.2	49	(% class="box warningmessage" %)
	50	(((
6.1	51	⚠ Note
16.2	52	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	53	\\[[image:login1.png\|\|alt="Untitled2.png" height="250" width="600"]]
23.2	54	)))
6.1	55
	56	== Via Direct URL ==
	57
13.1	58	You can also access Dependency-Track directly using the following link format:
23.1	59	[[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	60
	61	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.
	62
	63
26.1	64
	65	== Dependency-Track Jenkins Interaction ==
	66
	67	Nur sdcPipeline() wird unterstützt, nur maven (bisher), alles automatisch
	68
	69
26.2	70	== Collection Project und Unterprojekte ==
	71
6.1	72	= Users, Projects and Roles =
	73
13.1	74	* 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	75
	76	⚠ Note
13.1	77	Projects in the DevOps portal are mapped to the corresponding subwikis in Dependency-Track.
6.1	78
13.1	79	* 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	80	** Role mapping: (((
	81	\|=Project Role in DevOps Portal\|=Permissions in XWiki
24.1	82	\|Admin\| POLICY_VIOLATION_ANALYSIS,''VIEW_POLICY_VIOLATION,''VIEW_PORTFOLIO,'VIEW_VULNERABILITY,''VULNERABILITY_ANALYSIS'
6.1	83	\|Master\|(% colspan="1" %)Can view, comment, and edit pages, but cannot delete content
	84	\|Developer\|(% colspan="1" %)Similar to Master
	85	\|Viewer\|Read-only access. Can only view content, no edits or comments allowed
	86
	87	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/]]
	88	)))
	89
	90	= Main Features =
	91
24.1	92	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	93
	94	== Collaborative Content Editing ==
	95
	96	* WYSIWYG and wiki syntax editors
	97	* Version control and history tracking
	98	* Inline and structured content editing
	99	* Commenting and annotations
	100
	101	== Advanced Page & Document Management ==
	102
	103	* Hierarchical page structure (nested pages)
	104	* Templates for creating structured documents
	105	* Tags, categories, and metadata support
	106	* File attachments and preview
	107
	108	== Powerful Search and Navigation ==
	109
	110	* Full-text search (Solr-based)
	111	* Faceted search filters
	112	* Page index, breadcrumbs, and navigation panels
	113
	114	== Macros and Widgets ==
	115
	116	* Built-in and custom macros (charts, galleries, diagrams)
	117	* Embedding of rich media (videos, iframes, etc.)
	118	* Markdown and LaTeX support
	119
	120
	121
	122

Wiki source code of Dependency Track

DevOps-as-a-Service