I want to add several functionalities into this repo, but want to listen about your opinions first.

functionality 1 : enforce same dependency version in repo
Search from components, find all components with same `group` and `name`, but different `version` .If found any then fail. Otherwise succeed.
Might have an additional exclude mechanism
functionality 2 : enforce same dependency version as from one input sbom file.
functionality 3 : enforce license of components (blacklist and whitelist)

I see your codes, and seems I can do these codings myself. But I'm not sure:

1. may these functionalities merged into this repo? or I have to start another plugin repo?
2. should these functionalities be mojo, or be configurations inside of existing mojos? if you think it better to add mojos, should I add several seperate mojos, or 1 mojo with different configurations?

Review the existing mojos and how components are represented in the repository before choosing a scope. Clarify whether dependency-version and license enforcement belong in this plugin, whether they should be separate mojos or configurations, and how an input SBOM and exclusions would work. Done means maintainers have agreed on the scope and plugin design.

Written by the indexing model from the issue text.