# ladder mit Homebrew installieren Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für ladder in AI-Agent-Workflows. ## Installation ```sh sudo av install brew:ladder ``` Weitere Installationsbefehle: ### macOS - Homebrew (100%): ```sh brew install ladder ``` Evidenz: local Homebrew formula metadata ## Paketfakten - **Paketschlüssel:** brew:ladder - **Paketmanager:** Homebrew - **Version:** 0.0.23 - **Quellzusammenfassung:** Selfhosted alternative to 12ft.io and 1ft.io HTTP web proxies - **Homepage:** - **Repository:** - **Zuletzt aktualisiert:** 2026-07-26T13:40:58+02:00 - **Generiert:** 2026-08-03T19:37:03+00:00 ## Executables - ladder (Alias) ## Installationsverhalten - Bottle: nicht verfügbar ## Version und Aktualität - Seite generiert: 2026-08-03 - Manager-Version: 0.0.23 ## Projektgeschichte und Nutzung Ladder is a self-hosted HTTP web proxy for testing and analyzing paywall behavior, response modification, CORS/header behavior, and content delivery differences across client environments. The project positions itself for legitimate research, QA, and debugging use. Its package history is niche but concrete: a small Go proxy became a packaged binary, Docker image, Compose service, Helm-adjacent deployment, and ruleset-driven web tool. ### Projektgeschichte The README describes Ladder as a developer tool for simulating different client environments and observing how modern websites serve content under varying conditions. It supports request and response modifications, custom user agents, X-Forwarded-For settings, injected code, raw HTML fetching, an API route, and rulesets. The project separated reusable rules into the `everywall/ladder-rules` repository and release notes later mention ruleset compiler work, JSON body support, FlareSolverr integration, Docker hardening, and continued binary releases. ### Adoptionsgeschichte Ladder adoption appears concentrated among self-hosters, researchers, and developers who want a local or private proxy rather than depending on public hosted services. The README documents binary, Docker, Docker Compose, and Helm-chart installation paths. Release pages show early 0.0.x packaging with multi-platform assets and community contributions, but there is limited public evidence of broad institutional adoption. ### Wie es verwendet wird Users run the proxy locally or in Docker, often pointing it at a ruleset URL. They can browse through the web form, append a target URL to the proxy base URL, call `/api/`, or fetch raw HTML through `/raw/`. Configuration is mostly environment-variable driven: port, preforking, user agent, forwarded IP, basic auth, URL logging, allowed domains, base path, ruleset path, and optional FlareSolverr host. ### Warum Paket-Nerds sich dafür interessieren Ladder is package-nerd interesting because it packages an otherwise messy browser/proxy/debugging workflow into one self-hostable binary and container image. It also illustrates the tension around proxy tools in package repositories: useful for QA and access-control testing, but requiring explicit warnings about legal compliance, terms of service, and public-instance abuse. ### Zeitleiste - 2020s: Ladder emerged as a self-hosted alternative to public article-proxy services. - 2020s: The project added Docker, binary, API, ruleset, and response-modification workflows. - 2020s: The ruleset repository became a companion project for reusable domain-specific behavior. - 2026: The v0.0.x release line included JSON API body support, FlareSolverr integration, and Docker hardening work. ### Related projects - `everywall/ladder-rules` is the direct companion ruleset repository. - FlareSolverr is an optional integration mentioned by Ladder for browser-rendered challenge handling, with separate legal and contractual considerations. - Public services such as 12ft.io and 1ft.io are historical comparison points named by the package metadata and repository description. ### Quellen - - - - - ## Sicherheitshinweise Für ladder wurde kein passendes lokales Secret-Handling-Manifest gefunden. Nucleus-Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat. ## Combined YAML source View the package source record on GitHub. [combined/ladder.yml](https://github.com/mxcl/pkgdb/blob/main/combined/ladder.yml) ## Quellen - pkg.so package database - curated package history - pkgdb category and tag curation - cross-ecosystem install command graph