PHP Analyzer

A thorough PHP development toolkit for checking, validating, formatting, linting, and analyzing PHP code. Works entirely offline with local storage, zero configuration, and a clean command-line interface.

Why PHP Analyzer?

• Works entirely offline — your data never leaves your machine
• Simple command-line interface, no GUI needed
• 12 core PHP analysis commands plus utility commands
• Export to JSON, CSV, or plain text anytime
• Automatic history and activity logging

Commands

Each core command (check, validate, generate, format, lint, explain, convert, template, diff, preview, fix, report) works in two modes:

• Without arguments: shows recent entries from that command's log
• With arguments: records the input with a timestamp and saves to the command-specific log file

Data Storage

All data is stored locally at ~/.local/share/php-analyzer/. Each command maintains its own .log file (e.g., check.log, lint.log, format.log). A unified history.log tracks all activity across commands with timestamps. Use the export command to back up your data in JSON, CSV, or plain text format at any time.

Requirements

• Bash 4.0+ (uses set -euo pipefail)
• Standard Unix utilities: date, wc, du, tail, grep, sed, cat, basename
• No external dependencies or API keys required
• Works on Linux, macOS, and WSL

When to Use

1. PHP code review — Run php-analyzer check and php-analyzer lint to catch issues before committing code
2. Code formatting standardization — Use php-analyzer format to enforce consistent code style across a project
3. Migration assistance — Use php-analyzer convert and php-analyzer diff when upgrading PHP versions
4. Learning and debugging — Run php-analyzer explain to understand error messages or PHP patterns
5. Project reporting — Use php-analyzer report and php-analyzer stats to generate summaries of code quality over time

Examples

# Check a PHP file for issues
php-analyzer check "src/Controller/UserController.php — missing return type"

# Lint a directory of PHP files
php-analyzer lint "app/Models/*.php — unused imports detected"

# Format code to PSR-12 standard
php-analyzer format "src/Services/PaymentService.php — PSR-12 compliance"

# Generate a boilerplate class
php-analyzer generate "Laravel controller for OrderService with CRUD methods"

# Explain a PHP error
php-analyzer explain "Fatal error: Cannot use object of type stdClass as array"

# View statistics across all commands
php-analyzer stats

# Export all data as JSON
php-analyzer export json

# Search for a specific term in all logs
php-analyzer search "Controller"

# Check system health
php-analyzer status

Output

All commands return structured text to stdout. Redirect to a file with php-analyzer <command> > output.txt. Exported files are saved to the data directory with the chosen format extension.

Configuration

The data directory defaults to ~/.local/share/php-analyzer/. The tool auto-creates this directory on first run.

Powered by BytesAgain | bytesagain.com | hello@bytesagain.com