Our take
Activerecent releases- Activity
- 47
- Community
- 47
- Issues
- 36
- Pull requests
- 26
+253 stars in the last 30 days
- Slower to merge pull requests than 99% of the projects we track
Ladder is an actively maintained, configurable proxy for website behavior testing, with recent commits and releases and contributions from multiple people, though issue resolution can be slow.
Good fit if
- You need a self-hosted Go proxy to inspect or adjust headers, URLs, or HTML for testing.
- Domain-specific YAML rules and Docker deployment suit your workflow.
- You can operate it with access controls and follow its GPL-3.0 license terms.
Look elsewhere if
- You need a reliable way to defeat advanced bot detection or guarantee access to restricted content, which Ladder does not promise.
- You need the unfinished robots.txt testing feature, an optional TOR proxy, or shareable keyed URLs.
- You need a Windows binary with documented testing, or you cannot accommodate the project’s Go and Node.js requirements.
All health signals
| Last commit | 2026-10-13 (2 days ago) |
|---|---|
| Commits, last 90 days | 9 |
| Releases, last 12 months | 2 (latest v0.0.23, 2026-05-04) |
| Contributors | 16 (top contributor: 70% of commits) |
| Issues closed, last 90 days | 3 (typically closed in 92 days) |
| Pull requests merged, last 90 days | 5 (typically merged in 38 days) |
| Project age | 2 years |
Checked on 2026-10-16 with the GitHub API.
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
9,442Forks
543Change since Nov 17, 2026: +3 stars·0 forks
Overview
Ladder is a Go HTTP proxy and developer tool for testing and analyzing paywall implementations and content delivery on modern websites. It lets developers, researchers, and publishers inspect how a site responds to different client settings, then modify request headers, response headers, URLs, or HTML using domain-specific rules.
Use it to debug access controls and compare site behavior in controlled tests, not as a guarantee of access to restricted content. Ladder supports Docker, Linux and macOS binaries, and a Windows binary that the README describes as untested.
Key Features
- Emulate a client with a configurable User-Agent and
X-Forwarded-Foraddress. - Remove or change response headers, including CORS and Content-Security-Policy headers.
- Modify HTML with regular-expression rules or inject custom HTML, CSS, and JavaScript.
- Apply domain- and path-specific rules, including URL changes.
- Browse through the proxy, retrieve raw HTML, or make requests through its API.
- Restrict proxy use to an allowed domain list and protect access with Basic Auth.
- Optionally integrate with FlareSolverr for domains configured to use it.
Use Cases
- A publisher checks whether its paywall or access controls behave consistently for browser and crawler user agents.
- A web developer investigates CORS or Content-Security-Policy behavior while testing a site or its assets.
- A researcher compares content delivery across client settings for legitimate testing or analysis.
- A self-hosting team applies domain-specific page changes or URL rules while browsing through a controlled proxy.
What you need
Detected in the repository
- Node.js (from package.json)
- Go 1.26 or newer (from go.mod)
- A Dockerfile, so it can run in a container; a Compose file sets up the related services
- Automated checks on GitHub Actions
License in plain words
GPL-3.0strong copyleft
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the license notice
- Share your changes: yes, the full source of anything you distribute that includes it, under the GPL
- Includes an explicit patent grant from the contributors:
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
With Docker, start Ladder using the default ruleset:
docker run -p 8080:8080 -d --env RULESET=https://raw.githubusercontent.com/everywall/ladder-rules/main/ruleset.yaml --name ladder ghcr.io/everywall/ladder:latest
Then open http://localhost:8080. If the proxy will be publicly accessible, configure Basic Auth. See the README for binary, Compose, Helm, API, and ruleset instructions.
Considerations
The project is active, with recent commits and releases, and has contributions from 16 contributors; contribution activity is not concentrated in one person. Issue handling may take time, with a measured median close time of about three months. The README warns that advanced fingerprinting, rate limits, and behavioral checks can prevent successful requests; optional FlareSolverr integration is separate and adds latency and resource use. Robots.txt testing, TOR proxy support, and shareable proxied URLs are listed as unfinished. The GPL-3.0 license should be reviewed for your deployment and distribution plans.
Found this useful?
Share it with someone who would like ladder.