I am the author and maintainer of cargo-semver-checks, a linter for semantic versioning in Rust: cargo semver-checks && cargo publish

It prevents accidental breaking changes from frustrating users and maintainers: nobody likes a broken build, nor dealing with the fallout of publishing code that unexpectedly breaks for its users.

Sponsorships help me:

• Ship semver lints: cargo-semver-checks can currently catch 80+ kinds of issues, but there are hundreds more that still need to be implemented
• Ship optimizations: this one reduced a 5+ hour workload to 7.7s — over 2300x faster.
• Perform research on Rust semver edge cases and the kinds of semantic versioning accidents that happen in practice. Examples from my blog:
  • Breaking semver in Rust by adding a private type, or by adding an import
  • Re-exporting an enum with a type alias is breaking, but not major
  • Moving and re-exporting a Rust type can be a major breaking change
  • Some Rust breaking changes don't require a major version

If you're a current sponsor and would additionally like to fund the development of a specific feature with a one-time contribution, please reach out to me ahead of time via social media or email so we can coordinate. Contributions made without such coordination in advance cannot be directed toward funding the development of a specific feature.

If you need an invoice or any other documentation to make a sponsorship commitment, I'd be happy to get that sorted out with you.

I also built and maintain the Trustfall universal query engine which powers cargo-semver-checks. If you're interested in using it in your own work, please give me a ping!