SafeLine

chaitin/SafeLine

SafeLine is a self-hosted WAF(Web Application Firewall) / reverse proxy to protect your web apps from attacks and exploits.

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Sep 28, 2026
4 days ago
Ship score
78/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 22,393 → 22,685 (Aug 18 – Sep 29, 2026)
+212 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
22.7K
Forks
1.5K
Open issues
71
Watchers
110
Primary language
Go
Created
Apr 12, 2023
Owner
chaitin · 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

#api-gateway#application-security#appsec#blueteam#bruteforce#captcha#cve#cybersecurity#firewall#hackers#http-flood#security#self-hosted#sql-injection#vulnerability#waf#web-application-firewall#web-security#websecurity#xss

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on Sep 22, 2026 — os_startup 98%, self-hostable 96%, hosted offering 68%. 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.

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 chaitin/SafeLine, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/chaitin/SafeLine.svg)](https://ossean.com/chaitin/SafeLine)

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.