> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/developer-tools/snyk-cli/scan-and-maintain-projects-using-the-cli/snyk-cli-for-open-source/open-source-projects-that-must-be-built-before-testing-with-the-snyk-cli.md). # Open Source Projects that must be built before testing with the Snyk CLI Open Source Projects that must be built before testing with the Snyk CLI For some types of Open Source Projects, you must build the Project before testing it with the [Snyk CLI.](/developer-tools/snyk-cli/overview.md) Manifests provide some dependency information. However, other dependencies are resolved only after the Project is built. In addition, lockfiles giving dependency information may not be available before the Project is built. The following types of Projects must be built before testing with the CLI. | **Language** | **Project type** | **Build required?** | | ------------------- | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | JavaScript | npm |

Build required only if no package-lock.json file is present; run npm install to generate.
See the Snyk for JavaScript documentation for supported lockfile versions

| | JavaScript | pnpm | Build required only if no `pnpm-lock.yaml` file is present; run `pnpm install` to generate | | Javascript | Yarn | Build required only if no `yarn.lock` file is present; run `yarn install` to generate | | Java | Maven |

Yes
Run mvn install before testing.

| | Java | Gradle | No | | .NET | NuGet | Build required only if no `packages.config` file is present. | | .NET | Paket | Yes | | Python | pip |

Yes
Run pip install -r requirements.txt before testing. Install is required so that the full dependency tree (nested dependencies included) can be tested.

Alternatively, pass the CLI --skip-unresolved=true option when testing to test only the dependencies available without building.

| | Python | pipenv |

Yes
Run pipenv update before testing

| | Python | setup.py |

Yes
Run pip install -e . before testing

| | Python | Poetry |

Yes
If no Poetry lockfile exists, run poetry lock to generate a poetry.lock file before testing.
No
If the lockfile exists.

| | Python | dep |

Yes
Run dep ensure before testing.

| | Golang | Go Modules | No | | Swift / Objective-C | Cocoapods | Build required only if no `Podfile.lock` file is present; run `pod install` to generate | | Swift | Swift Package Manager | No | | Scala | sbt | No | | Ruby | Bundler | Build required only if no `Gemfile.lock` file present; run `bundle install` to generate. | | PHP | Composer | Build required only if no `composer.lock` file is present; run `composer install` to generate. | --- # 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://docs.snyk.io/developer-tools/snyk-cli/scan-and-maintain-projects-using-the-cli/snyk-cli-for-open-source/open-source-projects-that-must-be-built-before-testing-with-the-snyk-cli.md?ask=&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.