An audit report should still make sense after it’s been forwarded three times.
I’ve released SSRWire 0.5.0, with a new HTML report for handing over findings from streamed HTML checks.
Each built-in finding explains:
What was observed.
Why it matters.
What to change.
Fix examples can be tailored to Next.js, Nuxt, Astro, WordPress and other supported stacks. The framework choice changes the guidance; the findings still come from the captured response.
Response timings and metadata arrival order sit alongside those explanations, so a developer can inspect the evidence behind a finding.
npx ssrwire@0.5.0 check https://example.com \ --format html --output audit.html
The result is one HTML file that opens offline, without JavaScript or remote assets. Attach it to an issue, send it to a client, or keep it with the release checks.
Even the social-preview section stays local: it shows the captured metadata and image URL without fetching the image.
An audit report should still make sense after it’s been forwarded three times.
I’ve released SSRWire 0.5.0, with a new HTML report for handing over findings ...