> 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/getting-started/core-functionalities/display-license-issues-in-feed.md).

# Display License Issues in Feed

In addition to the license report, Aikido allows you to display licenses directly in the feed. These issues are grouped by license type and show all locations where a specific license is used. This feature helps you stay informed and take immediate action on license-related issues.

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

* Directly act licenses: snooze, ignore, or create tasks.
* Receive alerts for new critical and high severity license issues.

### How to enable Licenses in feed <a href="#how-to-enable-licenses-in-feed" id="how-to-enable-licenses-in-feed"></a>

**Step 1:** Navigate to the [License & SBOM Reports page](https://app.aikido.dev/licenses)

**Step 2:** Click the Action dropdown menu and select 'Display Licenses in Feed'

![Dropdown menu with option to display licenses in the feed.](https://3149773201-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyKbzcQGrx7UtrG0nPZZ7%2Fuploads%2Fgit-blob-e3ac3de12c552677333bf419ff9adcf64762ab42%2Fucarecdn-1b911e0a-9234-471b-8012-fb2db9f5bf3e.png?alt=media)

**Step 3:** Select one of the three options. You have the option to show only the critical licenses issues, or also including the high severity ones.

> **Note:** all issues in the feed are reflected in the trends over time report. This means that by enabling this functionality, there might be a bump in the number of open issues.

![License issue feed settings with options for filtering severity and reporting.](https://3149773201-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyKbzcQGrx7UtrG0nPZZ7%2Fuploads%2Fgit-blob-d6f5457beeb8749ba50c310ef61c7a29bcabbce0%2Fucarecdn-ec0a687f-41f4-4660-ba8d-66423429f333.png?alt=media)

**Step 4:** Go back to Feed and select License Issues in the filter. All open critical and/or high severity license issues will be displayed. **Aikido will run a scan in the background to start showing licenses - this can take a minute.**

![Security dashboard menu highlighting resolved License Issues.](https://3149773201-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyKbzcQGrx7UtrG0nPZZ7%2Fuploads%2Fgit-blob-e1c4819f8388c079fe38ed3324e82e68817fb52d%2Fucarecdn-d4b4064c-882a-40b5-b9c4-3b61ef5780ea.png?alt=media)


---

# 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/getting-started/core-functionalities/display-license-issues-in-feed.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.