Docker Hub API Gateway

01. Project Overview

Unified REST API gateway for Docker Hub — user stats, SVG cards, repo/tag lookup, OpenAPI docs, and interactive testing in English and Chinese.

02. Problem

Why build this?

Docker Hub data was fragmented — pull totals, repo details, and badges needed a single, documentable API surface for tools and READMEs.

03. Solution

How was it solved?

Shipped a Hono-based gateway with user stats, SVG cards, repo/tag APIs, OpenAPI docs, bilingual UI, and live request testing.

04. Architecture

System architecture

05. Key Features

Core capabilities

• User and repository stats APIs
• Embeddable Docker stats SVG cards
• Repo / tag lookup endpoints
• Interactive OpenAPI documentation
• Bilingual EN/ZH tester UI
• Dogfooded by this site’s live metrics

06. My Role

What did I specifically do?

• Designed the unified REST + SVG card contract for Hub data.
• Implemented the Hono gateway, OpenAPI docs, and bilingual tester.
• Wired production usage into this portfolio’s live metrics pipeline.

07. Tech Stack

What technologies power it?

• Hono
• TypeScript
• Vercel
• OpenAPI
• Docker Hub API

08. Metrics

What results can we show?

09. Deployment

How do you run it?

Deploy on Vercel and call the public REST / SVG endpoints.

1. Open the live gateway for interactive docs and testing.
2. Call /api/user/stats or embed the SVG docker-stats card in READMEs.
3. Clone the InnoNestX repo to self-host or extend the gateway.

10. GitHub

11. Live Demo

12. Tradeoffs

• Unified REST + SVG cards over scraping Hub HTML — stable for README embeds.
• OpenAPI + bilingual tester so callers can verify before wiring production.
• Dogfoods its own /api/stats — this site’s homepage metrics call the same gateway.

13. What shipped

• Public REST endpoints for user and repository stats
• Embeddable Docker stats SVG cards
• Interactive OpenAPI docs for real-time testing

14. Inspectable proof

15. Links