Hints for pdfarranger in universe

pdfarranger.desktop ⚙ all

asv-screenshot-no-media
pdfarranger.appdata.xml:26 -
A screenshot must contain at least one image or video in order to be useful. Please add an <image/> to it.
asv-component-summary-missing
pdfarranger.appdata.xml -
The component is missing a summary (<summary/> tag).
asv-component-name-missing
pdfarranger.appdata.xml -
The component is missing a name (<name/> tag).
asv-cid-desktopapp-is-not-rdns
pdfarranger.appdata.xml:13 - pdfarranger.desktop
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-unknown-tag
pdfarranger.appdata.xml:28 - updatecontact
Found invalid tag. Non-standard tags should be prefixed with `x-`. AppStream also provides the <custom/> tag to add arbitrary custom data to metainfo files. This tag is read by AppStream libraries and may be useful instead of defining new custom toplevel or `x-`-prefixed tags if you just want to add custom data to a metainfo file.
asv-id-tag-has-type
pdfarranger.appdata.xml:13 - pdfarranger.desktop
The <id/> tag still contains a `type` property, probably from an old conversion to the recent metainfo format.