The review follows the browser's whole outbound path.
A screenshot route does more than open its first URL. It resolves names, follows redirects, creates subrequests, and operates inside your network boundary. The review checks the public source at each point where untrusted input can become an outbound connection.
Schemes, URL credentials, hostname syntax, suffixes, ports, length, and normalization.
Request boundaryIPv4, IPv6, mapped addresses, loopback, private, link-local, metadata, and special-use ranges.
Destination policyAll-answer validation, mixed answers, lookup timing, rebinding exposure, and failure behavior.
Name resolutionInitial document, redirects, frames, and whether a validated name is resolved again at connection time.
Connection pathScripts, images, stylesheets, fonts, media, service workers, downloads, and background traffic.
Browser graphTimeout, queue, concurrency, dimensions, response size, context isolation, and cleanup.
Resource policyCaller authentication, action authorization, secret handling, error detail, logs, storage, and retention.
Ownership boundaryYou receive evidence, a patch, and the remaining boundary.
Risk-ranked findings
A concise Markdown review ties every finding to the public route, affected behavior, practical impact, and recommended control.
One focused hardening change
The agreed endpoint and its directly supporting validator or proxy helper are patched without redesigning unrelated application code.
Negative-path regression coverage
Focused tests cover the agreed public control plus relevant local, private, mixed-DNS, redirect, subrequest, or hygiene failures.
Verification, rollback, residual risk
The final note states what changed, how to verify it, the shortest rollback path, and what remains outside the fixed scope.
Additional endpoints, repositories, languages, live testing, architecture work, or new findings outside the agreed route require a separate owner-approved scope.
Inspect the report before sharing the route.
The public worked specimen reviews one intentionally vulnerable Playwright endpoint. It shows the finding rank, source evidence, patch gate, negative-path matrix, rollback record, and residual risk without naming a customer or claiming a live vulnerability.
- Critical
Arbitrary main-document, redirect, frame, and subrequest egress reaches
page.goto()without connection-time policy. - High
No caller authorization protects browser work; no queue, deadline, dimensions, or output cap bounds resource use.
- Patch gate
Choose a fixed-origin contract or whole-request-graph enforcement. A regex or one preflight lookup is not presented as sufficient.
- Evidence
Twelve positive and negative cases cover authorization, address families, mixed DNS, rebinding, redirects, subrequests, overload, and error hygiene.
The scope stays inside one public route.
Fits the review
- One existing screenshot or PDF endpoint in a public GitHub repository
- JavaScript, TypeScript, or Python source you control
- Controls and tests that can be assessed without secrets or production access
- A focused patch is possible inside the endpoint and its direct helper
Stops the review
- Private source, credentials, signed URLs, customer data, or production access
- Live exploitation, penetration testing, cloud-account review, or incident response
- Compliance certification, legal advice, an SLA, or a security guarantee
- Multiple endpoints, a proxy fleet, auth rewrite, storage redesign, or ongoing support
The completed review reduces a documented risk surface. It does not certify that the endpoint, repository, infrastructure, or application is vulnerability-free.
The owner confirms fit before payment or work begins.
- 1
Send public scope
Share the repository, one route path, runtime, current controls, test evidence, and the outcome you need. Do not include a secret, private URL, customer record, or production artifact.
- 2
Lock the review surface
The owner confirms the route, exact findings to cover, deliverables, exclusions, and whether a focused patch is feasible inside the fixed price.
- 3
Owner confirms payment and start
The owner handles payment separately and explicitly authorizes the start. Submitting this form does not take payment, reserve work, or grant repository access.
- 4
Review the handoff
You receive the report, patch, tests, verification and rollback notes, and one revision inside the agreed scope. You retain merge and deployment control.
Request the free scope check.
Share only public, non-sensitive source details. The intake lets the owner decide whether the route fits before either side commits to payment or work.