[Feature request]: expose verified/unverified status in CLI

[cassidyjames]

Checklist

• I agree to follow the Code of Conduct that this project adheres to.
• I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Suggestion

I'm admittedly not 100% sure how the verified status of an app from Flathub is exposed to the Flatpak CLI, but a user requested the Flatpak CLI could show whether apps are verified/unverified, similar to what GNOME Software does.

I figured I'd at least file this for discussion in case it could be implemented!

[chrisawi]

GNOME Software reads flathub::verification::verified from the appstream metadata. I'm not sure adding that to flatpak itself would be appropriate, at least as long as it's Flathub-specific.

Verification is currently only exposed in the flatpak CLI via subsets. You can either restrict Flathub to the verified subset with flatpak remote-modify, or add a second remote named e.g. flathub-verified with that subset set. In that case, you know if an app is verified if flatpak offers to install it from that remote. Clearly, both options have downsides.

It occurred to me that a generic solution would be to present the subset membership for each app. As it turns out, there's an existing request for that (#5320) and even an implementation in a branch from @TingPing.

It seems reasonable to also present that in flatpak install.

[cassidyjames]

@chrisawi ah, that makes sense as a generic implementation for Flatpak—thanks!