"Request: GitHub Verified Creator Status for Banking Environment

Request: GitHub Verified Creator Status for Banking Environment

Hi @paulhatch,

I hope this message finds you well. I'm reaching out from a banking institution where we're implementing CI/CD automation for our testing frameworks.

Current Situation

We discovered your semantic-version action while designing CI/CD automation for our testing frameworks. It would be an ideal solution for our semantic versioning needs, but our enterprise security policies restrict us to using only GitHub Verified Creators or pre-approved actions.

Current Approach

We've implemented a custom semantic versioning solution, but we'd prefer to use your established and well-maintained action if security compliance allowed it.

Request

Would you consider applying for GitHub Verified Creator status? This would enable organizations like ours (and likely many other enterprises) to use your action without requiring special security exceptions.

Benefits

• Broader adoption in enterprise environments
• Enhanced trust through GitHub verification
• Security compliance for banking/finance sector
• Professional recognition of your work

Our Use Case

We're developing automated npm package versioning for a banking test framework, and semantic versioning is a critical component of our release process.

Alternative

If verification isn't feasible, would you be open to suggestions for making the action more enterprise-friendly (security scanning, documentation improvements, etc.)?

Thank you for maintaining this valuable tool, and I understand if verification isn't a priority for you.

Best regards,
Daniel Drazan
CSOB

No repository file, test, or entry point is identified. Start by reviewing GitHub's Verified Creator requirements and the request's enterprise-security context; done would mean determining whether the action can pursue verification or documenting a concrete alternative.