Menu

Individual skill

audit-redirects

0upvotes

Find open redirects in pracht loaders, middleware, and navigation, including hand-rolled 3xx responses that bypass the built-in guards. Use for "audit redirects", "check for open redirects", "is my ?redirect= param safe", "review login redirects".

skills/audit-redirects/SKILL.md

Read pinned source

Source commit e7c088a615e0bc16659d7a307fe92910ae6bd546

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
108
Repository last updated
Nov 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Pracht Audit Redirects

The classic open-redirect bug: `/login?redirect=https://evil.example` →
after login, the app redirects the user to attacker territory carrying a fresh
session.

What the framework guarantees: the client router drops non-`http(s):` schemes
at the navigation boundary, and server-side `redirect()` /
`buildRedirectResponse()` reject non-`http(s):` schemes and CR/LF injection
against the `Location` header. What it cannot decide is whether the target
*origin or path* is one you trust — and a raw
`new Response(null, { status: 302, headers: { location: userInput } })`
bypasses all of those guards entirely.
Back to top