# Get more details on match suggestion

You can assess the likelihood that this is the correct match by viewing the trend of reported vulnerabilities over time and the known versions for this match suggestion. Multiple matches that have a trend of reported vulnerabilities and that match your dependency’s versions (or at least version formats) are considered stronger matches.

**Match details modal sections**

<table><thead><tr><th width="221.5">Section name</th><th>Description</th></tr></thead><tbody><tr><td>Reported vulnerabilities over time</td><td>Multiple matches that have a trend of reported vulnerabilities indicate that this is a frequently-used dependency. If you don’t see many reported vulnerabilities over time, it is likely that this is not the correct match. Check that the dependency’s versions (or at least version formats) are considered strong matches.</td></tr><tr><td>Known versions</td><td>These are the known versions for this suggested match that are coming from the CVE vulnerability ID. Check that your dependency’s versions (or at least version formats) match these. </td></tr></tbody></table>


---

# 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://helm.docs.medcrypt.com/~/changes/KjixZskptrAaNWiTYnvj/find-known-vulnerabilities/match-statuses/assess-match-suggestions/get-more-details-on-match-suggestion.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.