AppStream Report for PureOS - Issues for powersupply-gtk in landing/main

Errors

gui-app-without-icon
The component is a GUI application (application which has a .desktop file for the XDG menu and Type=Application), but we could not find a matching icon for this application.

missing-launchable-desktop-file
The MetaInfo file references a .desktop file with ID 'org.postmarketos.powersupply.desktop' in its launchable tag, but the file was not found in the same source tree. In order to be able to launch the software once it was installed, please place the MetaInfo file and its .desktop files in the same package.

asv-screenshot-media-url-not-secure
:20 - http://brixitcdn.net/metainfo/powersupply.png
Consider using a secure (HTTPS) URL to reference this screenshot image or video.

metainfo-no-summary
Component does not contain a short summary. Ensure that the components MetaInfo file has a summary tag, or that its .desktop file has a Comment= field set.
More information can be found in the Desktop Entry specification and the MetaInfo specification.

no-metainfo
This software component is missing a MetaInfo file to provide metadata.
We currently took some data from its desktop-entry file and the long description of the package it is located in.
This has several disadvantages, like poor markup, too technical descriptions for users of software centers, different components having the same description, etc.
Additionally, a lot of software with desktop-entry files should either not be installable and searchable via the software catalog (like desktop-specific settings applications) or be tagged accordingly via MetaInfo files.
Please consider to either hide this desktop-entry file from AppStream by adding a X-AppStream-Ignore=true field to it, or to write a MetaInfo file for this component and send it upstream.
Generating components from non-MetaInfo files is deprecated, if you do not add a MetaInfo file, this software may vanish from the metadata catalog (and if it is a GUI application, no longer be visible in software centers) in a future distribution release.
You can consult the MetaInfo quickstart guides for more information on how to write a MetaInfo file, or file a bug with the upstream author of this software component.