add protoc-gen-httpgo to Generators section

[MUlt1mate]

We want to ensure high quality of the packages. Make sure that you've checked the boxes below before sending a pull request.

• I have read the Contribution Guidelines
• I have read the Maintainers Note
• I have read the Quality Standards

Not every repository (project) will require every option, but most projects should. Check the Contribution Guidelines for details.

• The repo documentation has a pkg.go.dev link.
• The repo documentation has a coverage service link. see below
• The repo documentation has a goreportcard link.
• The repo has a version-numbered release and a go.mod file.
• The repo has a continuous integration process that automatically runs tests that must pass before new pull requests are merged.
• Continuous integration is used to attempt to catch issues prior to releasing this package to end-users.

Please provide some links to your package to ease the review

• forge link (github.com, gitlab.com, etc): https://github.com/MUlt1mate/protoc-gen-httpgo
• pkg.go.dev: https://pkg.go.dev/github.com/MUlt1mate/protoc-gen-httpgo
• goreportcard.com: https://goreportcard.com/report/github.com/MUlt1mate/protoc-gen-httpgo
• coverage service link (codecov, coveralls, etc.): see below

Pull Request content

• The package has been added to the list in alphabetical order.
• The package has an appropriate description with correct grammar.
• As far as I know, the package has not been listed here before.

Category quality

Note that new categories can be added only when there are 3 packages or more.

Packages added a long time ago might not meet the current guidelines anymore. It would be very helpful if you could check 3-5 packages above and below your submission to ensure that they also still meet the Quality Standards.

Please delete one of the following lines:

• The packages around my addition still meet the Quality Standards.

Thanks for your PR, you're awesome! 😎

Coverage note

The main module shows low coverage (approx. 2%) because standard coverage tools struggle to track execution within a protoc plugin lifecycle. Since the core logic involves generating Go source code and passing it back to the Protobuf compiler, traditional unit tests on the generator's internals are less effective than verifying the end result.

Instead of internal unit tests, I use a integration driven approach located in the example module.
What it does:

• generates HTTP servers/clients from a wide variety of .proto definitions.
• ensures the generated code compiles without errors.
• runs a bunch of unit and integration tests against the generated code to ensure the HTTP handlers, middlewares, and marshaling logic work as intended.

It runs within CI/CD and can be run local with make test and make run commands

[github-actions]

Automated Quality Checks (from CONTRIBUTING minimum standards)

• Repo: OK
• pkg.go.dev: OK
• goreportcard: OK (grade unknown)
• coverage: missing

These checks are a best-effort automation and do not replace human review.

[MUlt1mate]

Can someone please take a look at this PR and tell if my excuse for absent coverage is acceptable?
@phanirithvij hi! Sorry, you seem to be an active maintainer here. Can you help me?

[harmonseam-max]

Yes

…

On Mon, Jan 26, 2026 at 10:33 AM Mikhail ***@***.***> wrote: *MUlt1mate* left a comment (avelino/awesome-go#6004) <#6004 (comment)> Can someone please take a look at this PR and tell if my excuse for absent coverage is acceptable? @phanirithvij <https://github.com/phanirithvij> hi! Sorry, you seem to be an active maintainer here. Can you help me? — Reply to this email directly, view it on GitHub <#6004 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B4SEDN4GS2PNH75PS6MMV234IXNOLAVCNFSM6AAAAACSVCBVKWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOOJYGY2DMNRWGY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>