I Vibe Coded a GitHub Action — Then Turned It Into a Real Product

A few days ago, I had a simple thought:

Developers show how much they code all the time. But what if we showed what they actually ship?

GitHub profiles are full of contribution graphs, streaks, language statistics, commit counters, and activity widgets.

They are useful.

But they mostly answer questions like:

• How active is this developer?
• How often do they commit?
• Which languages do they use?

I wanted to answer a different question:

What has this developer actually delivered?

That idea became Proof of Shipping.

🔗 GitHub repository:

https://github.com/hamza-topo/proof-of-shipping

🔗 Live example on my GitHub profile:

https://github.com/hamza-topo

🔗 First public release:

https://github.com/hamza-topo/proof-of-shipping/releases/tag/v1.0.0

Proof of Shipping is a GitHub Action that analyzes real public GitHub activity and generates a visual card showing:

• published releases
• merged pull requests
• latest delivery
• activity over a configurable period

What it looks like in practice

Here is the card running on my actual GitHub profile:

![Proof of Shipping running on my GitHub profile]

This isn't a mockup.

The card is generated by the GitHub Action itself from my public activity.

At the time of writing, my profile shows:

• 0 releases during the selected period
• 7 merged pull requests
• my latest delivery from the petmingle repository

The workflow runs directly inside GitHub Actions and updates the SVG stored in the profile repository.

And yes, it is now on GitHub Marketplace

![Proof of Shipping on GitHub Marketplace]

The project eventually went from:

Idea → AI-assisted coding → tests → real integration → release → GitHub Marketplace.

And yes — a large part of the coding process involved AI.

But that is also where this project became interesting.

Because somewhere along the way, it stopped feeling like simple vibe coding and started requiring actual software engineering.