summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorMike Lewis <mlewis@gitlab.com>2019-06-21 16:30:43 +0000
committerGitLab Release Tools Bot <delivery-team+release-tools@gitlab.com>2019-06-25 16:25:00 +0000
commit25594d4169006adc2d13a546a874636c46a5de48 (patch)
treec78f1aa25477283a1a432e9233e2be9e0961bd43 /doc
parentf24e8f41d08b70b6aba9c7f42019aad56450ca8d (diff)
downloadgitlab-ce-25594d4169006adc2d13a546a874636c46a5de48.tar.gz
Merge branch 'docs/deps-gemansium' into 'master'
Remove Gemnasium dead link from docs See merge request gitlab-org/gitlab-ce!29942 (cherry picked from commit 76f49de4e772c4101bcb8df801ad9b7a78adcea7) a84a7233 Remove Gemnasium dead link from docs
Diffstat (limited to 'doc')
-rw-r--r--doc/user/application_security/dependency_scanning/index.md16
1 files changed, 8 insertions, 8 deletions
diff --git a/doc/user/application_security/dependency_scanning/index.md b/doc/user/application_security/dependency_scanning/index.md
index 34d4507210e..a4e5b19bdc7 100644
--- a/doc/user/application_security/dependency_scanning/index.md
+++ b/doc/user/application_security/dependency_scanning/index.md
@@ -346,7 +346,7 @@ the report JSON unless stated otherwise. Presence of optional fields depends on
| `vulnerabilities[].scanner` | A node that describes the analyzer used to find this vulnerability. |
| `vulnerabilities[].scanner.id` | Id of the scanner as a snake_case string. |
| `vulnerabilities[].scanner.name` | Name of the scanner, for display purposes. |
-| `vulnerabilities[].location` | A node that tells where the vulnerability is located. |
+| `vulnerabilities[].location` | A node that tells where the vulnerability is located. |
| `vulnerabilities[].location.file` | Path to the dependencies file (e.g., `yarn.lock`). Optional. |
| `vulnerabilities[].location.dependency` | A node that describes the dependency of a project where the vulnerability is located. |
| `vulnerabilities[].location.dependency.package` | A node that provides the information on the package where the vulnerability is located. |
@@ -379,17 +379,17 @@ Once a vulnerability is found, you can interact with it. Read more on how to
## Dependency List
-> [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/issues/10075)
-in [GitLab Ultimate](https://about.gitlab.com/pricing/) 12.0.
+> [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/issues/10075) in [GitLab Ultimate](https://about.gitlab.com/pricing/) 12.0.
-An additional benefit of Dependency Scanning is the ability to get a list of your project's dependencies with their versions.
+An additional benefit of Dependency Scanning is the ability to get a list of your
+project's dependencies with their versions. This list can be generated only for
+[languages and package managers](#supported-languages-and-package-managers)
+supported by Gemnasium.
-This list can be generated only for [languages and package managers](#supported-languages-and-package-managers) supported by [Gemnasium](https://gitlab.com/gitlab-org/security-products/gemnasium/general).
-
-To see the generated dependency list, navigate to the Dependency List page under your project's left sidebar menu **Project > Dependency List**.
+To see the generated dependency list, navigate to your project's **Project > Dependency List**.
## Contributing to the vulnerability database
You can search the [gemnasium-db](https://gitlab.com/gitlab-org/security-products/gemnasium-db) project
to find a vulnerability in the Gemnasium database.
-You can also [submit new vulnerabilities](https://gitlab.com/gitlab-org/security-products/gemnasium-db/blob/master/CONTRIBUTING.md). \ No newline at end of file
+You can also [submit new vulnerabilities](https://gitlab.com/gitlab-org/security-products/gemnasium-db/blob/master/CONTRIBUTING.md).