PhpCodeArcheology

Coding · tested 2026-08-26 · re-test due 2026-11-24 · by the Hlido desk, not the vendor

In short: A PHP static-analysis tool that measures architecture rather than just style — 60+ metrics, 14 problem detectors and six output formats — and is, by its own claim, the first PHP analyzer with a native MCP server and a generated CLAUDE.md.

5 PASS · 0 FAIL of 5 public-surface claims

Quick answer

PhpCodeArcheology scores 77/100 (STEADY) on Hlido’s independent, hands-on test (reviewed 2026-08-26). STEADY (77) because PhpCodeArcheology is a thorough, transparent architecture analyzer (60+ metrics with a formula glossary, 14 detectors, six formats incl.

PhpCodeArcheology positions itself past the linter tier: 60+ architecture and maintainability metrics (cyclomatic and cognitive complexity, maintainability index, LCOM, Halstead, instability, coupling, type coverage) computed per file, class, method and function, plus 14 problem detectors (god classes, dead code, circular dependencies, deep inheritance) flagged with error/warning/info severity and actionable descriptions. It is MIT, PHP 8.2–8.5, composer-installed, needs no extensions, and — unusually for this category — is framework-aware, reading composer.json to detect Symfony/Laravel/Doctrine and adjust thresholds so framework boilerplate does not generate false positives. Two features make it genuinely agent-relevant and lift the score: it ships a native MCP server (it claims to be the first PHP static-analysis tool with one) so an assistant can query hotspots, dependency graphs and refactoring priorities in natural language, and it generates a CLAUDE.md project overview an AI assistant can read before touching the code. The six output formats include SARIF for GitHub Code Scanning and a JSON path for CI, so it slots into existing pipelines. The honest limits: it is PHP-only by design, the '60+/14/first-with-MCP' figures are the project's own claims rather than independently benchmarked here, and self-authored metric thresholds are still self-authored. Within PHP, this is a thorough, transparent and unusually agent-forward analyzer.

Why STEADY

STEADY (77) because PhpCodeArcheology is a thorough, transparent architecture analyzer (60+ metrics with a formula glossary, 14 detectors, six formats incl. SARIF), is framework-aware to avoid false positives, and is genuinely agent-native — a native MCP server plus a generated CLAUDE.md. Held at 77 because it is PHP-only by design, the headline counts and 'first-with-MCP' claim are self-reported rather than benchmarked here, and its thresholds are self-authored.

Public-surface checklist

What we saw

4 screenshots captured by the Hlido engine during the reviewed run (run-2ea5b5fac0ede252-phpcodearcheology-github-io). Our own captures — not vendor marketing material.

PhpCodeArcheology — run screenshot 1 (home.png)
home.png
PhpCodeArcheology — run screenshot 2 (page__.png)
page__.png
PhpCodeArcheology — run screenshot 3 (page__features.png)
page__features.png
PhpCodeArcheology — run screenshot 4 (page__quickstart.png)
page__quickstart.png

What it does well

What it fails at

Best for

  • PHP teams maintaining long-lived codebases who need architecture and maintainability metrics, not just style checks
  • Engineers who want an AI assistant to query codebase health and refactoring priorities over MCP
  • CI pipelines that consume SARIF (GitHub Code Scanning) or JSON alongside architecture reports

Not recommended for

  • Non-PHP or polyglot codebases
  • Teams that only need a fast style linter rather than architecture metrics

Pricing & access

Derived from Hlido-held evidence only (engine checklist + editorial text); quotes are verbatim from the scorecard; not vendor-supplied; re-derived daily. Verify current prices on the vendor's pricing page. Last verified 2026-08-26.

Compared to

Agent relevance

CLI MCP Behavioral-testable

Agentic-Commerce Readiness 65/100 · INTEGRABLE

Independent readiness for agent delegation & transaction. How it’s scored · check live

Two agent paths: a native MCP server the assistant queries in natural language for hotspots, dependency graphs, health scores and refactoring priorities (MCP tool calls such as get_hotspots and get_refactoring priorities), and a generated CLAUDE.md the assistant reads before editing the codebase. Also runs as a composer-installed CLI producing JSON/SARIF for CI. Directly designed for AI-assisted PHP maintenance.

Agent-friendly score: 8/10

Evidence

scorecard.json · transparency passport · registry · methodology

More: compare agents · best of · developer tools · incident registry

Verdict by Hlido Editor, our automated editorial system · Method: public-surface-tier-1+editorial-narrative-v2 · Methodology version 2026.05 · Next review due 2026-11-24

How this page was produced. The scores, claim verdicts and evidence come from automated hands-on testing of the product’s public surface. The written analysis is drafted by an AI system, and pages publish without a person reviewing each one. Hlido publishes this record and answers for it — tell us if anything here is wrong and we will correct it.

Embed this trust badge

Hlido trust score

Live, always-current independent score — free to embed on your site or README. No vendor pays for placement.

Markdown

[![Hlido trust score](https://hlido.eu/badge/phpcodearcheology-phpcodearcheology.svg)](https://hlido.eu/check/?agent=phpcodearcheology-phpcodearcheology)

HTML

<a href="https://hlido.eu/check/?agent=phpcodearcheology-phpcodearcheology"><img src="https://hlido.eu/badge/phpcodearcheology-phpcodearcheology.svg" alt="Hlido trust score"></a>