Hints for paraview in main

org.paraview.ParaView ⚙ amd64

asv-url-not-secure
org.paraview.ParaView.appdata.xml:53 - http://paraview.org/
Consider using a secure (HTTPS) URL for this web link.
asv-screenshot-caption-too-long
org.paraview.ParaView.appdata.xml - This visualization was a finalist in the SC21 Visualization Showcase. Credits: Francesca Samel et al. at Los Alamos National Lab.
The screenshot caption is too long (should be <= 100 characters)
asv-screenshot-caption-too-long
org.paraview.ParaView.appdata.xml - Emergence of skin micro-wrinkles. Courtesy of Georges Limbert, University of Southampton, UK and University of Cape Town, South Africa.
The screenshot caption is too long (should be <= 100 characters)
asv-screenshot-caption-too-long
org.paraview.ParaView.appdata.xml - ParaView was used in Russell Taylor’s Comp 715: Visualization in the Sciences class at the University of North Carolina at Chapel Hill. Author: Jared Vicory et al.
The screenshot caption is too long (should be <= 100 characters)
asv-content-rating-missing
org.paraview.ParaView.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
org.paraview.ParaView.appdata.xml -
This component contains no `developer` element with information about its author.

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.