Sign in or sign up before continuing. Don't have an account yet? Register now to get started.
[FEEDBACK] The new Dependency Scanning Analyzer
<!--IssueSummary start-->
<details>
<summary>
Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards.
</summary>
- [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=523458)
</details>
<!--IssueSummary end-->
With our transition to SBOM-based dependency scanning feature we provide a [new Dependency Scanning analyzer](https://gitlab.com/gitlab-org/security-products/analyzers/dependency-scanning) as a replacement to the previous Gemnasium analyzer, which offers the following benefits:
- Increased language support. The deprecated Gemnasium analyzers are constrained to a small subset of Python and Java version support.
- Increased performance. Depending on the application, builds invoked by the Gemnasium analyzers can last for almost an hour, and be a duplicate effort.
- Smaller attack surface. To support its build capabilities, the Gemnasium analyzers are preloaded with a variety of dependencies. The new dependency-scanning analyzer removes a large amount of these dependencies that results in a more secure footprint.
- Simpler configuration. The deprecated Gemnasium analyzers frequently require the configuration of proxies, CA certificate bundles, and various other utilities to function correctly. The new solution removes many of these requirements.
This feature is currently in Beta. To ensure quality as the feature makes progress towards GA, we'd like to collect user feedback.
## :reminder_ribbon: How to give feedback
1. **Check existing feedback & known issues:** Before submitting, check to see if your feedback is already captured in the linked items, [known issues](#known-issues), or reported by someone else in one of the threads. If so, comment on the existing thread or leave an emoji reaction to show support.
2. **Start a new thread:** If your feedback is not listed, start a new thread with a descriptive title. Include relevant details, screenshots, and steps to reproduce the issue in expandable sections.
3. **Be Specific:** Provide as much detail as possible, including device/browser information, steps to reproduce, and expected vs. actual outcomes.
## :handshake: What you can expect from us
1. We **will read** all of your feedback.
2. We **may not respond** to all feedback directly.
3. We will **create issues** for repeatable bugs and assign a [priority](https://handbook.gitlab.com/handbook/security/security-operations/sirt/severity-matrix/#priority) based on [severity](https://handbook.gitlab.com/handbook/security/security-operations/sirt/severity-matrix/#severity).
## Known issues
- [No longer builds application or installs dependencies](https://gitlab.com/gitlab-org/gitlab/-/issues/523458#note_2391296194)
- https://gitlab.com/gitlab-org/gitlab/-/issues/532667+s
issue