-
That JSON was invalid and when I cleaned it up so it was valid, I noticed that GitHub is giving me a 404 error for the https://github.com/Monsterbirdlimited/soscap repository URL you used in it.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
mbncap
Discontinued capture program for mbn [Moved to: https://github.com/Monsterbirdlimited/soscap]
{ "app-id": "io.github.monsterbirdlimited.mbncap", "runtime": "org.gnome.Platform", "runtime-version": "43", "sdk": "org.gnome.Sdk", "command": "mbnmain.py", "finish-args": [ "--share=ipc", "--socket=x11", "--socket=pulseaudio", "--device=dri" ], "modules": [ { "name": "mbncap", "buildsystem": "simple", "build-commands": [ "install -Dm755 mbnmain.py -t /app/bin/" ], "sources": [ { "type": "git", "url": "https://github.com/Monsterbirdlimited/mbncap", "commit": "a5d3e5a0660fb666650f629688ac6578d5a90ce7" } ] } ] }
-
flatpak-external-data-checker
A tool for checking if the external data used in Flatpak manifests is still up to date
Another thing you could add would be to tag your releases on GitHub, add a tag field next to the commit one, and add an x-checker-data section to the manifest so the Flathub bot will automatically open PRs to update the Flatpak release when you update your repository.
-
Your Appstream XML and .desktop file are unsatisfyingly sparse. (Compare the ones from the aforementioned I Have No Tomatoes flatpak that I maintain.)