mrkeyoor.comAsk

fosrl/pangolintested 25 Aug 2026commit 7319bf8

pangolin review

Trial Pangolin if you need its documented combination of browser access and private resource access.

  • Build failed
111 sto install
  • 1,637 packages
Self-Hostedevaluationupdated 01 Nov 2026
+126stars / 7d

Consider Pangolin when you need browser access to applications and client access to private resources under one access policy. Our run on August 25, 2026, at commit 7319bf8 installed successfully but failed its source build. Our sandbox did not test a deployed gateway or working tunnels. Pangolin combines reverse-proxy and VPN capabilities with granular access control.

Verdict

Trial Pangolin if you need its documented combination of browser access and private resource access. Our August 25, 2026 run at commit 7319bf8 completed installation but failed the source build, and tests were skipped. Reproduce the build with the project's required setup or evaluate the documented containers with a small resource set, actual client networks, and a tested restore procedure before expanding access.

We ran it

Lab card: what happened when we ran pangolin
Lab card from our sandbox run
Screenshot of pangolin (pangolin.net)
pangolin.net
Install✓ · 111s1637 packages · 1580 MB
Build✗ · 30s
Testsn/ano test script
Known vulns140 critical · 1 high · 3 moderate · 10 low (npm audit)
Repo1874 files~313,530 lines of source · 30.2 MB · 5 CI workflows · Dockerfile · tests dir

Answers from our run

Does pangolin build from source?

Dependencies installed in 111 seconds (1637 packages), and the build failed. We cloned commit 7319bf8 into a clean Debian container with 3 CPUs and no project-specific setup.

Does pangolin have tests you can run?

Not through a standard command: the project exposes no test script or target that our harness could run.

Does pangolin have known vulnerabilities in its dependencies?

npm audit flagged 14 known advisories in the dependency tree at the time of our run.

Who should not use pangolin?

Teams requiring a demonstrated successful source build at commit 7319bf8.

What are the alternatives to pangolin?

NetBird, Tailscale. Trial Pangolin if you need its documented combination of browser access and private resource access.

Setup2/5Substantial unresolved friction: our source build failed, and the documented container installation was not tested.
Docs5/5Comprehensive within the supplied installation and update scope: prerequisites, setup, migrations, backups, and verification are explained.
Community4/5Last push on 2026-08-26 and 23,751 stars.Editor’s note: The supplied primary extracts do not establish contributor participation, support response times, or issue-resolution outcomes.
Maturity3/5Deployment and migration procedures describe an operational path, but our failed source build and untested deployment leave material qualifications.

How we score

Discussed on

  1. hnShow HN: Pangolin – Open source alternative to Cloudflare Tunnels500 points
  2. hnShow HN: Pangolin: Open-source identity-based VPN (Twingate/Zscaler alternative)81 points
  3. hnShow HN: Pangolin – SSO and WireGuard instead of API keys for LLM access3 points

Who it’s for

Operators who need browser-published applications and installed-client access to private resources.
Teams assigning users and roles to individual resources.
Self-hosters prepared to maintain a public gateway, DNS, containers, administrator accounts, and backups.

Who it’s NOT for

Teams requiring a demonstrated successful source build at commit 7319bf8.
Readers seeking measured tunnel reliability, throughput, or deployment security: our run assessed none of these.
Self-hosters without the public server, root access, domain, and firewall configuration required by the installation guide.

Setup reality

Our sandbox recorded npm installation success in 111 seconds, followed by build failure with exit code 1 after 30 seconds. Tests were skipped because the harness detected no test script. A tests directory existed; the skipped step does not establish that the repository had no tests.

The attached stored parser summaries report 1,637 dependency packages occupying 1,580 MB and 14 npm audit advisories: 1 high, 3 moderate, 10 low, and none critical. The raw installation footer contains different package and advisory totals. Their scopes remain unreconciled, so the footer does not replace the stored summaries. Audit scan coverage is unknown because scannedPackages is absent.

The documented container installer requires a Linux server with root access and a public IP, a domain pointing to it, an email address, and open TCP ports 80 and 443 plus UDP ports 51820 and 21820. Our sandbox did not run that installer.

Should you trial Pangolin?

Pangolin combines reverse-proxy and VPN capabilities with granular access control. Consider a limited trial if you need both browser access to applications and installed-client access to private resources. Our failed source build leaves deployment readiness unresolved.

The README at our recorded commit describes these access paths, NAT traversal, and permissions assigned to specific resources. Those are documented capabilities. Our sandbox did not verify application access, authentication, client connections, or access-policy enforcement.

What our sandbox recorded

Our run on August 25, 2026, at commit 7319bf8 installed successfully but failed its source build. The full commit was 7319bf84f78c33d94490d24a85b5441d7db15d44. Installation returned exit code 0 in 111 seconds; the build returned exit code 1 after 30 seconds. Neither command timed out.

Our harness records command outcomes, exit codes, elapsed time, timeout status, and retained log tails. A successful installation command does not establish that a gateway started or served a workload. The build tail repeatedly references module-not-found diagnostics beside application page paths, but it does not name the missing modules or establish the cause. Peer-dependency warnings and pending install-script approvals also appear in the installation tail; their presence does not prove that they caused the build failure.

Tests were skipped because the harness detected no test script. The checkout contained a tests directory, so this is a limitation of the recorded execution rather than evidence that no tests existed. We have no passing or failing test count for this run.

No new execution was performed for this correction. Our sandbox did not deploy the published containers, connect sites or clients, exercise NAT traversal, benchmark throughput, or conduct a security review. The MrKeyoor testing methodology explains the reporting approach and its limits; its current description does not establish which methodology version the August run used. The attached sandbox image label and detected Node major also differ, so this record does not establish a verified Node runtime version for reproduction.

What the dependency record establishes

The attached stored parser summaries report 1,637 dependency packages occupying 1,580 MB and 14 npm audit advisories: 1 high, 3 moderate, 10 low, and none critical. These are the attached dated harness values, preserved without substituting the different totals in the raw installation footer.

The supplied evidence does not reconcile the footer with the summaries. Do not add their totals together or treat either package total as verified audit coverage. The audit record lacks scannedPackages, so scan coverage is unknown. The advisories are recorded dependency findings, not proof of exploitable flaws in a deployed Pangolin gateway. Stored parser summaries also do not establish unique or exhaustive test coverage.

Where public ports are still required

Self-hosting Pangolin requires a public gateway with open firewall ports. The quick-install guide specifies a Linux server with root access and a public IP, a domain pointing to it, an email address, TCP ports 80 and 443, and UDP ports 51820 and 21820.

The pinned README's description of outbound tunnels without public IPs or open ports concerns protected sites. It does not remove the gateway requirements. The installer pulls Pangolin, Gerbil, and Traefik images; Gerbil is optional for a standard reverse-proxy deployment without tunneling. These documented container steps were not part of our npm source run.

Which alternatives deserve comparison?

NetBird combines a peer-to-peer private network with centralized access control. Its current README also lists browser SSH and RDP, a reverse proxy with automatic TLS, and self-hosting. Compare it directly when those requirements overlap your Pangolin evaluation. The supplied evidence does not establish which platform is easier to operate or more reliable.

Tailscale provides private WireGuard networks. Its repository contains the daemon and CLI used by its clients. Consider it when private device connectivity is your main requirement. The supplied extract does not establish replacement coverage for Pangolin's browser publishing; a separately retained application proxy would complement that networking choice. We did not run either alternative.

What to verify before expanding a trial

The pinned README identifies Community Edition as AGPL-3 and Enterprise Edition as using the Fossorial Commercial License. It states that Enterprise Edition is free for personal and hobbyist use and businesses below $100K USD gross annual revenue. Check the applicable edition and license terms before deployment.

The update guide requires backups and explains that migrations can prevent downgrades; a failed database migration blocks startup. Start with a small resource set, verify permissions with separate user accounts, connect from the networks your users actually use, and test restoration before expanding access. These are recommended next steps, not completed sandbox checks.

How the scores are assessed

The editorial rubric runs from 1 to 5: 1 indicates a blocker without a demonstrated route through it; 2 indicates substantial unresolved friction; 3 indicates an operational path with material qualifications; 4 indicates strong evidence with limited gaps; 5 indicates comprehensive evidence within an explicitly bounded scope. Unknown dimensions receive no numerical score. These ratings are judgments about the supplied evidence, not benchmarks or adoption measurements.

Setup ease is 2 because our source build failed and the container installation remains untested here. Documentation is 5 within the supplied installation and update scope, which covers prerequisites, setup, migrations, backups, and verification. Community is unassessed because the extracts do not establish contributor participation or support outcomes. Maturity is 3 because operational procedures are documented, while our failed build and lack of deployment testing leave material qualifications.

Alternatives

ProjectWhat it isPick it when
NetBird gh↗A peer-to-peer private network with centralized access control and documented browser-access and reverse-proxy features.Compare it directly when private networking, browser SSH or RDP, and reverse-proxy access overlap your requirements.
Tailscale gh↗Private WireGuard networking with a daemon, CLI, and client applications.Consider it for private device connectivity; separately verify how your browser-publishing requirements will be met.

What people are saying

  1. [github-trending] fosrl/pangolin

Sources

  1. Pangolin repository and README
  2. Pangolin quick install guide
  3. Pangolin update guide
  4. Pangolin 1.21.1 release
  5. Relayed local connection report
  6. Apple client disconnection report
  7. Dual-stack mobile connection report

More self-hosted reviews