There are good options if you don't care about historical analytics, like py-cov-action/python-coverage-comment-action.

From a security perspective you may not want a bot controlled by the GitHub token of the current repo owner to be in a GitHub Actions Workflow, as Bad Actors could use it [potentially] to spam every PR and issue in your repository.

If you care about historical analytics, AI-driven quality improvement recommendation, and scope-creep—e.g., security scanning tooling, linting, &etc.—then pay for our SaaS =]

See our pricing page for more details. Discounts available for enterprise orders.

If successful in gaining [free] cloud credits, I'll offer at cost to these groups (i.e., $0).

See the repository root for a copy of the licenses. We are (Apache-2.0 OR MIT) licensed; enabling free-use in private and commercial settings; and without the copyleft requirement of your changes being proferred back to us.

With that said, contributions welcome =)