Feedback wanted - early release (v0.1.5, now on Marketplace)

[rein051521]

maintainer-safe-ops is an early-stage CLI and GitHub Action for safer open-source maintainer workflows — pre-publish, pre-merge, and pre-release checks. It is not a replacement for gitleaks or CodeQL; it complements them by catching obvious mistakes before a release (a committed .env, rm -rf /, a risky pull_request_target workflow, curl ... | bash, or missing OSS readiness files).

If you try it, I'd love feedback on:

• false positives or false negatives you hit
• rules you'd like added
• whether the GitHub Action was easy to adopt in your repo

Quick start: see the README and examples/consumer-workflow.yml. Latest release: v0.1.3.

Thanks for taking a look!

[rein051521]

Update: maintainer-safe-ops is now published on the GitHub Marketplace (v0.1.5):
https://github.com/marketplace/actions/maintainer-safe-ops

It runs a quick pre-publish / pre-merge / pre-release check on a repository and flags common maintainer mistakes. It is a lightweight complement to dedicated scanners, not a replacement.

This is still an early release, and honest feedback is very welcome — especially:

• false positives you run into
• risky patterns it failed to catch
• rules you wish it had
• friction during setup or adoption

There is also a tracking issue for this: #24. Rough notes are fine; no praise needed.