Reports & Checklists / BROWSER-ONLY UTILITY
Security Report Builder
A report should tell a maintainer what you observed, how you know and what needs attention. Turn your existing notes into a structured document without inventing missing evidence.
Enter a report title, scope and limitations, then add your findings with evidence, impact and remediation. Include only observations you are authorised to document. Limit: 100,000 characters.
Loading local tool code...
Input stays in this tab. No upload, AI call, analytics or ads. Reset clears the workspace. Clipboard copies and downloaded files remain under your control.
Result
Technical details (optional)
Review the result before sharing. It may still contain personal or confidential information.
Evidence belongs before a severity label
The builder uses the severity you supply. It does not calculate a score or infer that a configuration warning can be exploited. If all you have is a static observation, say so in the evidence and limitations. Avoid presenting an untested possibility as a confirmed incident.
Fill in the scope before the findings
Use the title to identify the review, then describe which systems, versions or artefacts were included and which were not. Add limitations such as source-only review or no runtime testing. A maintainer needs to know whether your evidence came from source, staging or production. The sample deliberately describes a synthetic configuration, not a live test.
Write remediation someone can act on
Name the setting or behaviour to review, explain the intended outcome and identify how the maintainer can verify it. Do not prescribe a disruptive change just because it silences a checker. Include constraints when a framework, integration or business requirement affects the fix.
Review before sending
The export escapes user-supplied formatting that could become active HTML or misleading links. That does not remove confidential information from your prose. Check names, tokens, screenshots and URLs before sharing. Downloaded files remain wherever your browser saves them until you remove them yourself.
References
Documentation reviewed: . Rule results describe the supplied text, not a live application test.
Useful next steps
Maintained by MetaCyberGuru. A review point may need source, runtime or deployment context before you act on it.