I agree that the search on the Components page is very limited and could use some improvements. But what exact use-case can you currently not perform good enough to comply with CIS Control 6.4? Dependency Track does exactly what is stated in the requirements:

Establish and manage an updated inventory of third-party components used in development, often referred to as a “bill of materials,” as well as components slated for future use. This inventory is to include any risks that each third-party component could pose. Evaluate the list at least monthly to identify any changes or updates to these components, and validate that the component is still supported.

@valentijnscholten I would like the posibility to go trough the complete list, to insure that each component has:

1. Risk associated with component (Risk Score)
2. Whether component is supported (Version/Latest Version) - Future enhancement add depecrated true/false column?

As stated by the CIS assessment specification of safeguard 16.4

We're also interested into having a way to show all the components (across all projects) to manage the outdated libraries at a higher level.
As dependency-track force us to create a project for each couple Repository/Branch it also means we'll need a way to filter out some projects from this list.