php-vuln-scanner

Scan composer.json and composer.lock for known PHP dependency vulnerabilities.

386|38|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/0xShe/PHP-Code-Audit-Skill --skill php-vuln-scanner-0xshe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: php-vuln-scanner
Source: https://github.com/0xShe/PHP-Code-Audit-Skill/tree/main/php-vuln-scanner
Command: npx skills add https://github.com/0xShe/PHP-Code-Audit-Skill --skill php-vuln-scanner-0xshe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PHP projects often rely on numerous dependencies whose security posture is not always visible. This skill automates the detection of known PHP component vulnerabilities by scanning composer metadata and advisories, helping teams surface risk early and plan remediation.

Core Features & Use Cases

  • Composer-based detection: scans composer.json and composer.lock to identify vulnerable dependencies, including transitive ones.
  • Advisory matching: cross-references CVEs and vendor advisories to surface relevant risk context.
  • Reporting & traceability: outputs a structured vulnerability report with affected versions, routes to remediation, and evidence pointers for audit.
  • Use Case: Integrate with CI to fail builds when critical vulnerabilities are detected and generate compliance-ready reports.

Quick Start

Run the vulnerability scanner on your PHP project to produce a vulnerability report for the current dependency set.

Frequently Asked Questions about php-vuln-scanner

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

FAQPage Schema
How do I scan PHP dependencies for known vulnerabilities in composer.lock?

To scan PHP dependencies for vulnerabilities, parse composer.json and composer.lock files to identify affected packages and cross-reference them against CVE advisories. This process produces a consolidated vulnerability report with traceable references for remediation.

What is the best way to detect CVEs in transitive PHP dependencies?

Detecting CVEs in transitive PHP dependencies requires scanning nested modules within multi-module projects. By analyzing the full composer dependency tree against vendor advisories, you can surface hidden risks in indirect packages and generate a consolidated report.

Can I generate a compliance-ready security audit report for a PHP project?

Yes, you can generate a compliance-ready PHP security audit report by matching composer metadata against CVE advisories and internal rules. The output is a timestamped markdown report containing affected versions and evidence pointers for audit.

Does PHP vulnerability scanning work with multi-module projects?

PHP vulnerability scanning supports multi-module projects by parsing composer.json and composer.lock across nested modules. It maps transitive dependencies and consolidates the findings into a single vulnerability report with traceable references.

How do I fail a CI build when critical PHP dependency vulnerabilities are found?

To fail a CI build for critical PHP dependency vulnerabilities, integrate a scanner that cross-references composer.lock against CVE advisories. It detects critical risks and outputs a structured report, which you can use as a CI gate to halt vulnerable deployments.