Detect Gogs

PluginView evaluates public page signals in these classes when identifying Gogs. Individual fingerprint rule bodies are proprietary and are not published.

• Cookies
• Meta tags
• Script sources
• HTML markup

Illustrative indicators derived from public catalog metadata for Gogs. A live scan may match additional proprietary rules beyond these examples.

• i_like_gogits
• keywords: go, git, self-hosted, gogs
• js/gogs.js
• <div class="ui left">\n © 0 Gogs Version: Page:
• <button class="ui basic clone button" id="repo-clone-ssh" data-link="go…

Establishes

One or more public signals on the scanned page matched a known Gogs signature (5 rules) at the time of the scan.

Does not establish

A sitewide install of Gogs, an active vendor contract, exclusive use, or that Gogs is still in place today.

1. 1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest Gogs signals.
2. 2. PluginView reads only public responses (cookies, meta tags, script sources) and scores them against the Gogs signature set (5 rules).
3. 3. Review the confidence score and text explanation for Gogs on the results page.

A confirmed Gogs match also implies these technologies are present.

GoMacaron

Can PluginView detect Gogs without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Gogs — typically cookies, meta tags, script sources, html markup. It does not bypass authentication or paywalls.

What category is Gogs?

Gogs is classified under Development in the PluginView directory.

How many fingerprint rules cover Gogs?

This reference currently tracks 5 fingerprint rules across cookies, meta tags, script sources, html markup. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Gogs?

Illustrative public indicators for Gogs include i_like_gogits; keywords: go, git, self-hosted, gogs; js/gogs.js. A live scan may match additional proprietary rules beyond these examples.