New check: Does the project use protected tags?, blocked on GitHub feature implementation. about scorecard HOT 6 OPEN

@gabibguti I'm working through older issues to see which still have interest. PRs are welcome for any work, but the maintainers will not be focused on this work in the near future.

from scorecard.

Updating GitHub community discussion link:
https://github.com/orgs/community/discussions/10906
It's still on beta, but seems like it's not being watched/maintained.

from scorecard.

This feature does not align with the current project focus. If there is no feedback in the next 7 days to the contrary, then this issue will be closed.

from scorecard.

@afmarcum Just to clarify, you mean using the GitHub rulesets for restricting who can create, update and delete tags inside Scorecard repository does not align with Scorecard's focus right now, right?

Does it make sense to integrate the GitHub rulesets logic for Scorecard Branch-Protection check though?

from scorecard.

One advantage I see is, now that Scorecard has a contributor ladder, we could consider restricting the access for new maintainers on releasing by restricting the access to creating tags with GitHub rulesets.

from scorecard.

@afmarcum Just to clarify, you mean using the GitHub rulesets for restricting who can create, update and delete tags inside Scorecard repository does not align with Scorecard's focus right now, right?

Does it make sense to integrate the GitHub rulesets logic for Scorecard Branch-Protection check though?

Seems like the GitHub rulesets are already being considered for Branch-Protection, #3354. 🎉

from scorecard.