Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
I don't remember. I can only recall following my hosts instructions for installing it. I haven't had any notifications about expiry and Let's Encrypt sign in didn't recognise my email address.
At present, I've been distributing the single certsage.php file and all the primary instructions and resources in release posts in the #client-dev category. This has mainly been for search optimization, associating the safety of the community with CertSage, and collecting any bugs, questions, comments, concerns, suggestions, etc. in the community where they can be addressed within the community platform. There is a private GitHub project for CertSage with some experimental code. I haven't centralized there because I feel like many users of CertSage who aren't tech-oriented prefer the friendliness of the community to GitHub's ways. I will likely develop a website at the official domain (certsage.com) at some point. All the references in the code currently point to griffin.software, which itself needs a website and is only an entity for email and legal purposes right now.
@griffin You can of course do both: have CertSages code development at Github, but have the user oriented "front end" here on the Community. You can link to raw files on Github, although I haven't found a way to download the file instead of just viewing the file.. Of course users can use the right mouse button and use "save as" though.