Settings > About> stripes-final-form version is not displayed

, yep, all those points is a good idea but until it starts to cause a real problem (or a bigger problem than this, as you say) I don't think it will happen. 

The /_/proxy... endpoints don't help us here because stripes-form and stripes-final-form don't have any dependencies, and hence no module descriptor to register. 

Thanks , I didn't pay attention to the dependencies

I also remembered that we have //_/proxy/tenants/:tenantname/modules endpoint, but it only returns stripes-core and stripes-smart-components

seems like a good idea, we can also cover these web components with tests, currently not many components in stripes-core have them

Having stripes-final-form version in Settings would be nice, it just seems that doing is too much work just for this small change.

stripes-core sits below stripes-final-form in the dependency hierarchy, i.e. stripes-core is unaware of the existence of stripes-final-form, which is why its version is not displayed. Same goes for stripes-form, stripes-smart-components, and stripes-util. The only way to implement this would be to split stripes-core into separate modules (), one what remains inside @folio/stripes and acts like stripes-components and exports components for use by other apps, and one this is sth like ui-stripes-core that acts like a regular UI app and is responsible for displaying the welcome about "About: Versions" pages.