This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
Fibgen
Auto-generate OpenAPI docs from Go Fiber code — no comments
fibgen generates a complete OpenAPI 3.1 / 3.0 spec for Go Fiber services — with zero annotations. No @Summary comments, no codegen, no changes to your handlers. Point it at your project and get paths, params, request bodies, per-status responses, and resolved type schemas ($ref, enums, nullables). Fiber handlers are opaque at runtime, so fibgen reads the code itself via go/types, recovering types from your c.Bind() and c.JSON() calls. Fiber v2 & v3. Open source, MIT
Hey Product Hunt 👋
I built fibgen because keeping Swagger annotations in sync with handler code is a chore — and they rot the moment someone forgets a comment. I wanted docs that come from the actual code, not a parallel description of it.
The hard part: Fiber handlers are completely opaque at the type level (func(c fiber.Ctx) error), so there's nothing to reflect on at runtime. fibgen does real static analysis — it walks the route registrations, resolves group prefixes through variables, enters the handler body, and pulls types out of the c.* calls.
Would love feedback on which patterns it should learn next — interprocedural analysis (following respondJSON(c, user) helpers) is top of my list. What would make this a daily driver for you?
About Fibgen on Product Hunt
“Auto-generate OpenAPI docs from Go Fiber code — no comments”
Fibgen was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #135 on the daily leaderboard. fibgen generates a complete OpenAPI 3.1 / 3.0 spec for Go Fiber services — with zero annotations. No @Summary comments, no codegen, no changes to your handlers. Point it at your project and get paths, params, request bodies, per-status responses, and resolved type schemas ($ref, enums, nullables). Fiber handlers are opaque at runtime, so fibgen reads the code itself via go/types, recovering types from your c.Bind() and c.JSON() calls. Fiber v2 & v3. Open source, MIT
On the analytics side, Fibgen competes within API, Open Source and GitHub — topics that collectively have 208.3k followers on Product Hunt. The dashboard above tracks how Fibgen performed against the three products that launched closest to it on the same day.
Who hunted Fibgen?
Fibgen was hunted by Xackerr. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of Fibgen including community comment highlights and product details, visit the product overview.
Xackerr