Static Form Inspector

The useful part is its restraint. Static Form Inspector points to specific source problems, but it does not claim that a clean result proves a form will deliver. That makes it a sensible first check before a real endpoint test, especially for static sites where a broken form can otherwise look finished.

Paste one or more complete form elements into the browser tool to inspect their source. In the built-in broken example, the tool found an inert action and a placeholder credential, then warned about GET submission and unnamed fields.

The linked GitHub Action brings those checks into CI. Teams can choose failure thresholds and request a JSON report for later steps.

Developers who maintain static sites and want a quick check before sending a real submission through the form.

Teams that want common form mistakes to appear in repository checks instead of relying on a final manual review.

Static Form Inspector handles one narrow job well: catching visible source mistakes before they become delivery surprises. A clean report is still the start of testing, not proof that the form works end to end.