> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/admin-guide/32/continuous-integration/code-repo-scanning.md).

# Code repo scanning

Both twistcli and the Jenkins plugin can evaluate package dependencies in your code repositories for vulnerabilities.

The runtimes supported are:

* Go
* Java
* Node.js
* Python
* Ruby

## Integrate code scanning into CI builds

Point the Jenkins plugin to your code repo in the build directory.

**Prerequisites:** You’ve [installed and configured the Prisma Cloud Jenkins plugin](/admin-guide/32/continuous-integration/jenkins-plugin.md).

1. In your Jenkins job configuration, click **Add build step**, and select **Scan Prisma Cloud Code Repositories**.
2. Configure the repo scan.

   <figure><img src="/files/rqXLi2Zi1CvZM7tu3WVM" alt="code repo scanning config scan"><figcaption></figcaption></figure>

   1. In **Repository Name**, specify the name to be used when reporting the results in Console.
   2. In **Repository path**, specify the path to the repo in the build directory.

      For example, it could simply be the current working directory (`.`) or some relative directory.
3. Click **Save**, and then execute a build job.

   To see the scan results, log into Console, and go to **Monitor > Vulnerabilities > Code repositories > CI**. Prisma Cloud evaluates the contents of the repo according to the policy you’ve specified in **Defend Vulnerabilities > Code repositories > CI**. Prisma Cloud ships with a single default rule that alerts on all vulnerabilities.

   <figure><img src="/files/9uta3fVSNortU9m3nbEc" alt="code repo scanning results"><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.prismacloud.io/admin-guide/32/continuous-integration/code-repo-scanning.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.