> For the complete documentation index, see [llms.txt](https://docs.meterian.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.meterian.io/the-meterian-webapp/advanced-functionalities/set-exclusion/set-exclusions-report-page.md).

# From the report page

**Set an exclusion from the report page**

In the **Security** section, find the desired vulnerability, open the Actions tab and click on one of the options:

![](/files/-MLh_ksXc37GlcILtKSR)

In the **Stability** section, click on the Ignore button related to the library you want to ignore:

![](/files/-MHM94DvXbYeq4bm7tlh)

In the **Licensing** section, click on the Exclude button related to the library you want to exclude:

![](/files/-MHM9S4Kn6Vlm2D8za8c)

When required, remember to type a meaningful description before confirming the exclusion:

![](/files/-MHMGZOgUGO5KFl1gsMk)

**Trust a component**

In the security assessment, it is also possible to mark a specific component as **Trusted** so that all the transitive vulnerabilities, the ones carried by its dependencies, dot not affect the security score of the project.

{% hint style="info" %}
The vulnerabilities related to the component itself will be included in the security assessment.
{% endhint %}

To mark a component as **Trusted** simply open the Hierarchy tab (if present), hover on the component to mark as Trusted and a "Trust component" button will appear.

![](/files/AXnBuyqF1h1QdLCPFguf)

When required, remember to type a meaningful description before confirming the exclusion:

![](/files/hL2nZZOZ9sfw5ebKV6rq)

This type exclusion will, in every case, trigger a recompute of the security section of the report.