hidden

dwarvesf/hidden

An ultra-light MacOS utility that helps hide menu bar icons

Ship status

Still shipping

Pushed in the last 30 days.

Last push
31 Oct 2026
11 days ago
Ship score
67/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 15,021 → 15,372 (29 Sep – 10 Nov 2026)
+213 stars in the 28 days to 10 Nov 2026

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
15.4K
Forks
537
Open issues
141
Watchers
57
Primary language
Swift
Created
12 Feb 2019
Owner
dwarvesf · 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. 13 startups in the directory ship primarily in Swift.

Topics

#macos#swift#utilities

How it got here

What the classifier decided, and when.

Read by Jev, TypeSafe’s classifier, on 22 Sep 2026, which did not call this an open-source startup — it chose something else instead, and put os_startup at 30% (self-hostable 26%, hosted offering 18%). 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 Sep 2025 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: shipping — last push 31 Oct 2026This is the badge for dwarvesf/hidden, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/dwarvesf/hidden.svg)](https://ossean.com/dwarvesf/hidden)

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.