g-helper

seerge/g-helper

Lightweight Armoury Crate alternative for Asus laptops with nearly the same functionality. Works with ROG Zephyrus, Flow, TUF, Strix, Scar, ProArt, Vivobook, Zenbook, Expertbook, ROG Ally, and more.

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Sep 28, 2026
4 days ago
Ship score
96/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 14,777 → 15,375 (Aug 18 – Sep 29, 2026)
+407 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
15.4K
Forks
608
Open issues
116
Watchers
65
Primary language
C#
Created
Feb 10, 2023
Owner
seerge · User

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. 12 startups in the directory ship primarily in C#.

Topics

#ally#amd#armoury#asus#aura#cpu#fan#g-helper#g14#g16#ghelper#gpu#intel#mux#nvidia#overclock#power#rog#strix#tuf

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 44% (self-hostable 17%, hosted offering 9%). 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: shipping — last push 2026-09-28This is the badge for seerge/g-helper, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/seerge/g-helper.svg)](https://ossean.com/seerge/g-helper)

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.