php-route-tracer

Trace PHP route execution paths and parameter flow to data sinks.

80|6|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/yunmengya/PHP_AUDIT_SKILLS --skill php-route-tracer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: php-route-tracer
Source: https://github.com/yunmengya/PHP_AUDIT_SKILLS/tree/main/php-route-tracer
Command: npx skills add https://github.com/yunmengya/PHP_AUDIT_SKILLS --skill php-route-tracer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the complex process of tracing execution paths and data flow within PHP applications, starting from defined routes.

Core Features & Use Cases

  • Call Chain Tracing: Maps out the sequence of function and method calls originating from a specific route.
  • Parameter Flow Analysis: Tracks how data (parameters) moves from their source through variables to their final use (sinks).
  • Sink Identification: Pinpoints critical points in the code where external data is used, which are often potential security vulnerabilities.
  • Evidence Generation: Outputs detailed, verifiable evidence chains for each route, including source, taint propagation, sink, and validation logic.
  • Use Case: For a given web application route like /users/profile, this Skill will generate a report detailing every function called, how user input flows into those functions, and where that input is ultimately used, highlighting any sanitization or validation steps.

Quick Start

Use the php-route-tracer skill to trace the call chain and parameter flow for the route '/api/v1/users'.

Frequently Asked Questions about php-route-tracer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I trace PHP route execution paths and track data flow to sinks?

To trace PHP route execution paths and data flow, you provide the project root directory and optionally a routes.json file. The tool maps controller actions, cross-file calls, and parameter propagation to identify data sinks.

What is taint analysis and how does it find security vulnerabilities in PHP applications?

Taint analysis tracks how external data moves from sources through variables to final sinks, pinpointing critical code points where unsanitized input is used. It generates verifiable evidence chains highlighting validation logic for security auditing.

How do I generate verifiable evidence chains for PHP route call graphs?

Generate verifiable evidence chains by analyzing controller actions and cross-file function calls originating from defined routes. The output details the source, taint propagation, sinks, and associated validation steps for each path.

Do I need a routes.json file to perform parameter flow analysis on my PHP project?

You do not strictly need a routes.json file to perform parameter flow analysis, as providing the project root directory is required, but supplying a routes.json file optionally helps define specific entry points for tracing.

What's the best way to audit cross-file and cross-class method calls originating from a web route?

The best way to audit cross-file method calls is to trace call chains starting from a specific route. This maps the sequence of function calls and tracks user input propagation through variables to its ultimate use.