Some naive questions

If it's a hobby project then why would you care about any of this stuff? This kind of tool is mostly relevant for commercial software vendors who are charging money and need to manage the risks associated with licensing and incorporating FOSS into their products, to encourage them to be more choosy and not randomly grab stuff just because they can without thinking more about the lifecycle and future maintenance. Why else would you care to attest that the source code repository thoroughly describes the CI process unless you need to prove that to a downstream user of your code? If you have users who *need* this for compliance reasons then why can't they contribute to the maintenance manpower required to make it happen?

A lot of people feel social obligations around the code that they freely share and some commercial vendors take advantage of that to treat contributors like employees they don't have to pay, which is a recipe for unnecessary stress and burnout, especially when vendors use FOSS in critical infrastructure, then try to hold individual developers accountable for maintenance when it was the vendors choice to license FOSS in the first place.