Does PHPStan have an HTML error format?

No. Its built-in formats are table, raw, checkstyle, json, prettyJson, junit, gitlab, github and teamcity. The route to HTML is `--error-format=junit` into `junit2html`, or Checkstyle XML into a Checkstyle renderer.

Which format converts best?

JUnit, because the converters are ubiquitous and a PHPStan finding maps cleanly onto a failed case. Checkstyle is the better choice only if something else in your pipeline already reads it.

How do I keep the baseline out of the report?

Run the report against the same config your gate uses. If you have `phpstan-baseline.neon` in `includes`, the report shows what the baseline doesn't cover — which is usually what you want to publish.

Should the report step fail the build?

No. Suffix it with `|| true` and keep a separate unmuted `phpstan analyse` step as the gate, so a reporting problem never looks like an analysis failure.

How do I show progress raising the level?

PATCH one report id per repo and let the revision history carry it. Going from level 5 to level 6 is a diff between two revisions rather than a claim in a standup.

Share a PHPStan report

Raising a PHPStan level is a project, not a commit. Level 6 on a codebase that has been at level 5 for two years produces a few hundred findings, most of them one-line fixes, none of them assignable from a terminal dump.

PHPStan won't write HTML. It will write JUnit, and JUnit converts.

JUnit → HTML

composer require --dev phpstan/phpstan
pip install junit2html

./vendor/bin/phpstan analyse --error-format=junit > phpstan.xml || true
junit2html phpstan.xml phpstan.html

Or Checkstyle, if the pipeline already speaks it

./vendor/bin/phpstan analyse --error-format=checkstyle > phpstan-checkstyle.xml || true

Then feed it to whatever renders Checkstyle in your stack. Same destination, one fewer new dependency — see sharing a Checkstyle report.

Either way, || true is load-bearing: phpstan analyse exits non-zero on any finding, and the run with findings is the one worth publishing.

Publish it

Drag phpstan.html into the app, or from CI:

curl -fsS -X PATCH "https://commareports.com/api/v1/reports/$REPORT_ID" \
  -H "Authorization: Bearer $COMMA_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d "$(jq -n --rawfile html phpstan.html \
        --arg title "PHPStan L$LEVEL — $GITHUB_REF_NAME" '{title: $title, html: $html}')"

Raising the level, visibly

Keep one report id per repo and PATCH it weekly. The revision history becomes the record of a level bump: the run before, the runs in between, the run where the count hit zero and the baseline got deleted.

Anchored threads on a cluster of findings, so "these are all the same missing generic annotation on the repository interface" is written once, next to them. See commenting on HTML.
A routine re-running the analysis on a schedule so nobody has to remember.

Limits

Entry HTML: 5 MB. Assets: 25 MB per file, 250 MB and 500 files total. A first run at a higher level is the one that gets close — analyse one directory for the shareable view.
60 requests/minute per token.

Try it

Comma is free — unlimited reports, unlimited commenters, unlimited revision history.

Publish a static analysis report →