> For the complete documentation index, see [llms.txt](https://docs.aquilax.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aquilax.ai/user-manual/scanners/license-scanning.md).

# License Scanning

This documentation describes the AquilaX compliance process for detecting and handling license mismatching violations in software projects. The process is powered by the AquilaX GenAI Application Security Platform, leveraging AI to ensure comprehensive and efficient license compliance.

### **Objective**

To automate and streamline license scanning using AquilaX's platform, identifying mismatched or incompatible licenses across all project dependencies to ensure compliance with organizational and legal standards.

### **Process Overview**

#### **1. Initialization**

The license scanning module in AquilaX begins by integrating with your project's repository, extracting all declared and transitive dependencies, and identifying associated licenses.

#### **2. License Policy Definition**

AquilaX allows organizations to define license compliance policies, which include:

* Approved licenses (e.g., MIT, Apache 2.0).
* Restricted or incompatible licenses (e.g., AGPL, proprietary licenses).
* Exceptions based on use cases or environments.

#### **3. Scanning Process**

The scanning process includes:

1. **Dependency Detection:** Parsing dependency manifests (e.g., `package.json`, `pom.xml`, `requirements.txt`) and lockfiles.
2. **License Identification:** Mapping dependencies to their respective licenses via SPDX metadata or project-specific files.
3. **Policy Matching:** Comparing each dependency license against the defined compliance policy.
4. **Violation Reporting:** Flagging mismatched licenses and providing detailed violation reports.

#### **4. Remediation**

AquilaX provides:

* Suggested remediation steps for replacing non-compliant libraries.
* Automated license override workflows where applicable.


---

# 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.aquilax.ai/user-manual/scanners/license-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.