Website supply chain security

See which third parties run on your public pages and decide what belongs there.

For developers and site owners reviewing analytics, chat widgets, embeds, or scripts inherited from a previous team.

See a sample report

Order this review

US$19 · one-time

One public website. A report with evidence and recommended fixes.

One payment through Stripe

What the audit covers

Third-party inventory
See external origins and visible scripts loaded by key public pages.
Browser safeguards
Review visible controls such as content security policy and script integrity attributes where applicable.
Dependency priorities
Get a list of external dependencies to confirm, restrict or remove, with the evidence behind each item.

See what you’ll receive

See where each external origin appears, what it seems to do, and whether to confirm ownership, keep it, or investigate it.

Third-party script inventory and review notes

Illustrative example · Fictional website

Confirm ownerchat.example.net · support widget
The home and pricing pages loaded this script. Verify the vendor account and whether both pages still need the widget.
Reviewmetrics.example.org · analytics
The script appeared on the guide page. Check its consent behavior and confirm that the team still uses the data.
Check controlsstatic.example.com · embedded media
The samples show an external embed. Review the allowed origins and relevant browser controls with the site owner.

From website to report

  1. Enter your website. Use the public address for a site you manage or have permission to review.
  2. Pay US$19 once. Stripe confirms your order and collects the contact email for the report.
  3. Review the findings. Use the evidence and next steps to decide what to fix with your team.

Scope and common questions

What is included?

Review the third-party scripts and services visible on your website. See what visitors load, where it comes from, and which dependencies deserve review. The inventory covers dependencies a browser can see on sampled pages. Private packages, source repositories, and build pipelines fall outside this review.

Does a website address cover my entire software supply chain?

This review covers dependencies visible to a visitor. Server-side packages, build pipelines and private repositories require separate access and scope.

Will this catch every script?

The inventory reflects the sampled pages and states used in the review. Some scripts only load after consent, interactions, or a sign-in.

Can I use this for a vendor cleanup?

Yes. The origin, sampled page, and suggested action give you a starting point for asking owners to confirm or remove unused services.