# Binaries

A specific plugin can be activated in order to scan binaries and archives in a project using the parameter \
\&#xNAN;**`--scan-binaries`**

When activated the scanner will find all (recognised) archives, will then detect all (recognised) binaries present in such archives listing them in the report

The archives format recognised are:

* .war 
* .ear
* .aar
* .deb
* .tar
* .tar.xz
* .tbz2
* .tar.bz2
* .tgz
* .zip

The binaries format recognised are:

* .jar (java archives) -> java
* .dll (dynamic link libraries) -> cpp
* .whl (python wheel files) -> python

#### **Specific controls**

Two specific controls are availalbe for this scanner:

* `binaries.archives.extensions`\
  controls the archive formats recognised (by default, all)
* binaries.scanners.extensions\
  controls the binaries format taken in consideration (by default, all)

So, for example, if you want to restritct to a "java" only binary scanning, you could use these flags:

`-flags:binaries.archives.extensions=war,,ear,binaries.scanners.extensions=jar`


---

# Agent Instructions: 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:

```
GET https://docs.meterian.io/languages-support/binaries.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.