> For the complete documentation index, see [llms.txt](https://help.aikido.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aikido.dev/code-scanning/scanning-practices/dependency-scanning-for-bazel.md).

# Dependency Scanning for Bazel

With Bazel, you can import dependencies from a variety of sources, such as Maven repositories, Git repositories, or internal artifact registries. This is typically achieved using dependency rules like `http_jar`, `maven_install` .

Aikido supports scanning the targets you define within Bazel for security vulnerabilities. A build is not required, which speeds up the analysis process.

There are a limited amount of Bazel rules we currently support, but we're extending support along the way. Contact our team in case you want to suggest new Bazel rules to support.

#### Supported Bazel rules

Currently, we scan for dependencies imported via the following Bazel rules:

<table><thead><tr><th width="184.8897705078125">Bazel Rule</th><th>Note</th><th>Version</th></tr></thead><tbody><tr><td><code>java_library</code></td><td><ul><li><p>Analyzes the dependency-related attributes to identify dependencies brought in via the following dependency rules:</p><ul><li><code>maven_install</code></li></ul></li></ul></td><td><ul><li>Bazel >= 5</li></ul></td></tr><tr><td><code>rules_jvm_external</code></td><td><ul><li>Parses the lock file referenced in the `lock_file` attribute of `maven.install(...)` definitions. View details <a href="https://github.com/bazel-contrib/rules_jvm_external?tab=readme-ov-file#pinning-artifacts-and-integration-with-bazels-downloader"><strong>here</strong></a>.</li></ul></td><td><ul><li>Bazel >= 5</li></ul></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.aikido.dev/code-scanning/scanning-practices/dependency-scanning-for-bazel.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.