Hints for gfm in main

gfm ⚙ amd64

asv-cid-desktopapp-is-not-rdns
gfm.appdata.xml:4 - gfm
The component ID is not a reverse domain-name. Please update the ID to avoid future issues and be compatible with all AppStream implementations. You may also consider to update the name of the accompanying .desktop file to follow the latest version of the Desktop-Entry specification and use a rDNS name for it as well. In any case, do not forget to mention the new desktop-entry in a <launchable/> tag for this component to keep the application launchable from software centers and the .desktop file data associated with the metainfo data.
asv-desktop-app-launchable-missing
gfm.appdata.xml -
This `desktop-application` component is missing a `desktop-id` launchable tag. This means that this application can not be launched and has no association with its desktop-entry file. It also means no icon data or category information from the desktop-entry file will be available, which will result in this application being ignored entirely.

asv-screenshot-media-url-not-secure
gfm.appdata.xml:38 - http://lpg.ticalc.org/prj_tilp/images/gfm_main_upscaled.png
Consider using a secure (HTTPS) URL to reference this screenshot image or video.
asv-url-not-secure
gfm.appdata.xml:41 - http://lpg.ticalc.org/prj_gfm/
Consider using a secure (HTTPS) URL for this web link.
asv-content-rating-missing
gfm.appdata.xml -
This component has no `content_rating` tag to provide age rating information. You can generate the tag data online by answering a few questions at https://hughsie.github.io/oars/
asv-developer-info-missing
gfm.appdata.xml -
This component contains no `developer` element with information about its author.