> 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/c-c-lockfile-less-scanning.md).

# C/C++ Lockfile-Less Scanning

In many C/C++ projects, libraries are often included directly in the source code folder. Our product offers a unique lockfile-less scanning method to address this issue effectively.

### Benefits <a href="#benefits" id="benefits"></a>

* **Comprehensive Coverage**: Unlike most SAST tools, Aikido scans C/C++ libraries included in the source code folder. This ensures that no dependencies go untracked, enhancing the security of your codebase.
* **Accurate Matching**: By hashing all relevant files in the repository, we can accurately match your project's dependencies with a database of the most popular open-source libraries.
* **Detection of Modified Libraries**: Even if you have made small edits to a library or if a small file is missing, our tool can still detect the library version and match it correctly.

### How It Works <a href="#how-it-works" id="how-it-works"></a>

1. **Database of Open Source Libraries**: We maintain a large database of popular open-source libraries, including all its versions and files.
2. **Hashing Source Files**: When a repository is scanned, our tool hashes all relevant C/C++ files in the project. These hashes are then compared with the hashes in our database.
3. **Matching and Detection**: If there are sufficient matches between the hashes from the project and those in the database, we identify the library versions that are used.


---

# 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/c-c-lockfile-less-scanning.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.