OpenGFW

apernet/OpenGFW

This repository is in the OSSEAN directory, but it has no description on GitHub.

Ship status

Gone silent
Last push
No push on record
Days since that push unknown
Stars, last 7 weeks
Stars, weekly: 0 → 0 (Aug 25 – Oct 6, 2026)
+0 stars in the 28 days to 2026-10-06

GitHub reports this repository as gone. That forces the status to silent whatever the last push says.

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
0
Forks
0
Open issues
0
Watchers
0
Primary language
Unspecified
License
Unknown
Created
Jan 1, 1970
Owner
apernet

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. License unknown — GitHub’s own license field, not legal advice. This repo does not expose a primary language.

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 something else instead, and put os_startup at 4% (self-hostable 70%, hosted offering 15%). 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 2026-10-10This is the badge for apernet/OpenGFW, as served from the URL below.
[![OSSEAN: silent](https://ossean.com/badge/apernet/OpenGFW.svg)](https://ossean.com/apernet/OpenGFW)

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.