JBoss EAP 6 had BOMs with <groupId>org.jboss.bom.eap</groupId> [1].

When migrating an application from EAP 6 to EAP 7.0, we have no rules to search for these artifacts and suggest the version to move to.

Some help could arrive from EAP 7.0 Migration Guide to figure out the JavaEE 7 artifacts to suggest to migrate to.

Then, if the user is migrating to EAP 7.3, the rules should promote to the adoption of Jakarta EE 8 BOMs.

There's also the case of BOMs not available anymore like org.jboss.bom.wfk (i.e. Red Hat Web Framework Kit) one which has been dismissed. [2]
For such an artifact, we could have a "rewrite" rule when updating to EAP 7, based on the component the application needs from WFK: for example Arquillian might be available in some way in EAP 7 but RichFaces might be replaced as not available in EAP 7 at all.

[1] https://repo.maven.apache.org/maven2/org/jboss/bom/eap/
[2] https://access.redhat.com/solutions/1314313