expand the scope of the tool and rename it to sq-linter
In #13 (closed) I proposed expanding the scope of the tool to all OpenPGP data and renaming it to sq-linter.
My argument for the scope expansion is simply that in OpenPGP there can be issues with more than just keyring packets. For e.g. a signature (including a self-signature) can be done using an obsolete hash like SHA1 or MD5. In addition the tool already checks some signatures; i.e self-signatures on a key. I expect there are other problems with other packet types but don't have to the experience to know what they are.
@nwalfield mentioned they don't plan to work on this.
I also don't plan to work on this but I prepared a branch for the renaming, it could get merged once there are is some non-keyring OpenPGP data validation.