> 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:
In the **Stability** section, click on the Ignore button related to the library you want to ignore:
In the **Licensing** section, click on the Exclude button related to the library you want to exclude:
Following your click to exclude findings a modal will appear to customise and confirm it:
You must add a description to your exclusion. Then you can choose:
* its type,
* whether to apply the exclusion to all branches of the project and.
* its expiry date
**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.
When clicked a modal will appear requiring you to add a meaningful description, chose an expiry date and deciding whether the exclusion should apply to all the branches of the project:
This type exclusion will, in every case, trigger a recompute of the security section of the report.
