forbidden mit Homebrew, Nix installieren

Projektlinks

• Homepage

Befehle und Aliase

• forbidden
• stresser

Projektgeschichte

The public project history available from official sources is mostly README-level rather than narrative. The maintained README documents a mature command set, a v13.4 build artifact in source-install instructions, and a roadmap of future tests such as hop-by-hop headers, User-Agent headers, cookies, HTTP smuggling, CRLF, Log4j, and AWS metadata SSRF.

Adoptionsgeschichte

The README positions pip as the standard installation route and mentions a Homebrew formula as an alternative that is not maintained by the author. That combination places Forbidden in the common pentesting-tool distribution pattern of upstream Python packaging plus downstream CLI formulas.

Wie es verwendet wird

Typical use is to supply a target URL and choose test groups such as protocols, methods, uploads, overrides, headers, path mutations, encodings, authentication bypasses, redirects, and parser tests. The README cautions about proxies normalizing URLs, rate limiting, anti-bot protections, and engine-specific behavior.

Warum Paket-Nerds sich dafür interessieren

Forbidden is package-nerd relevant as a compact example of a Python security CLI that depends on multiple HTTP engines to exercise edge cases that ordinary curl invocations cannot always produce, such as duplicate Host headers or requests without a Host header.

Zeitleiste

• v13.4: README source-install instructions reference building forbidden-13.4-py3-none-any.whl.
• Current README: Homebrew installation is documented as an alternative not maintained by the author.

Related projects

• The README names Python Requests, PycURL, and Python HTTP Client as implementation engines and links to internal forbidden.py, test.py, and value.py files for the test definitions.

Quellen

• https://github.com/ivan-sincek/forbidden
• https://raw.githubusercontent.com/ivan-sincek/forbidden/main/README.md