pangolin

fosrl/pangolin

Modern networking and security platform providing secure access and connectivity to apps, infrastructure, and AI workloads. Connect and protect your users.

Ship status

Still shipping

Pushed in the last 30 days.

Last push
11 Nov 2026
1 day ago
Ship score
95/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 22,948 → 23,512 (29 Sep – 10 Nov 2026)
+444 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
23.6K
Forks
830
Open issues
122
Watchers
69
Primary language
TypeScript
License
Other
Created
27 Sep 2024
Owner
fosrl · Organization

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. 212 startups in the directory ship primarily in TypeScript.

Topics

#ai-gateway#gateway#nat-traversal#oidc#pam#pangolin#remote-access#reverse-proxy#sase#self-hosted#single-sign-on#ssh#sso#tunneling#vpn#wireguard#wireguard-vpn#zero-trust#zero-trust-network-access#ztna

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on 22 Sep 2026 — os_startup 99%, self-hostable 39%, hosted offering 60%. 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 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 11 Nov 2026This is the badge for fosrl/pangolin, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/fosrl/pangolin.svg)](https://ossean.com/fosrl/pangolin)

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.