MailHog

mailhog/MailHog

Web and API based SMTP testing

Ship status

Gone silent

No push in over 120 days. A quiet repo may also be a finished one.

Last push
Feb 13, 2024
962 days ago
Stars, last 7 weeks
Stars, weekly: 16,123 → 16,169 (Aug 18 – Sep 29, 2026)
+27 stars in the 28 days to 2026-09-29

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
16.2K
Forks
1.2K
Open issues
255
Watchers
156
Primary language
Go
Created
Apr 16, 2014
Owner
mailhog · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 99 startups in the directory ship primarily in Go.

Topics

This repository has no GitHub topics.

How it got here

What the classifier decided, and when.

Read by Jev, TypeSafe’s classifier, on Sep 22, 2026, which did not call this an open-source startup — it chose a package or library instead, and put os_startup at 5% (self-hostable 86%, hosted offering 11%). The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory. This one is in that queue, waiting for a person — removing a listing is a pull request a human opens.

Listed since the 2025-09 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: silent — last push 2024-02-13This is the badge for mailhog/MailHog, as served from the URL below.
[![OSSEAN: silent](https://ossean.com/badge/mailhog/MailHog.svg)](https://ossean.com/mailhog/MailHog)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.