Skip to content

Update index page with links to key concepts #141

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nscuro merged 1 commit into from
Jun 7, 2026
+16 −0
Merged

Update index page with links to key concepts #141

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions docs/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,15 @@ hide:
Dependency-Track is an intelligent component analysis platform
that allows organizations to identify and reduce risk in the software supply chain.

Built around the Bill of Materials (BOM) concept,
it tracks component usage across every version of every project in your portfolio
and surfaces known vulnerabilities, policy violations, and licensing risk as they emerge.
An API-first design makes it a natural fit for CI/CD pipelines.

!!! info "Documentation version"
This documentation covers Dependency-Track v5.
For v4, see the [v4 documentation](../4.x/).

## Getting started

Get Dependency-Track running locally in minutes with the [quick start tutorial](tutorials/quickstart.md).
Expand All @@ -20,6 +29,13 @@ Explore the documentation using the navigation tabs:
- [Concepts](concepts/index.md): background material on how Dependency-Track works.
- [Reference](reference/index.md): technical descriptions of APIs, configuration, and internals.

## Key concepts

- [Projects](concepts/projects.md): how Dependency-Track models the software you track.
- [Vulnerability findings](concepts/vulnerability-findings.md): how known vulnerabilities are surfaced and triaged.
- [Component policies](concepts/component-policies.md): codify what's acceptable in your portfolio.
- [Access control](concepts/access-control.md): teams, permissions, and project hierarchy.

## Coming from v4?

See [About changes in v5](concepts/changes-in-v5.md) for what changed and why,
Expand Down