Global and project aggregate statistics - A unique count of the components is missing

Right now DT only reports the aggregate component statistics from each project. If I understand correctly the logic is that any component in an independet project is an indepedent risk and issue in itself.

### Current Behavior:

As such the numbers vastly differ:

When in reality there are only:

Considering only the libraries:

### Proposed Behavior:
Show global Aggregate Statistics. A unique component count and global aggregate statistics should be pretty easy to implement in both SQL and API endpoint . Unique statistics would also help at the project level.

When is a component considered as an indepdent component in a project? Because there are often many duplicates. What values are considered unique in order to make a component its own component and not be considered a duplicate?
Or is this "duplication" intentional by the same logic that there are no aggregate global stats?