third-party-detector

What problem does it solve?

It detects and categorizes third-party services embedded in a website so you can understand what external vendors power payments, analytics, identity, CRM, and support.

Core Features & Use Cases

• Service Identification by Signals: Maps script URLs, JavaScript globals, CSP domains, DNS TXT records, and job-posting mentions to known third-party vendors.
• Category-Level Coverage: Produces results grouped by functional areas like payments, analytics, monitoring, authentication, and customer support.
• Explainable Evidence: Returns the specific signal types (e.g., script_url, js_global, csp_domain, dns_txt) that drove each finding, enabling audit-style validation.
• Use Case: When inheriting an existing web app, quickly compile a vendor list for compliance review, security assessment, and integration inventory.

Quick Start

Use the third-party-detector skill on Phase 2 raw signals to output a categorized list of detected third-party services with supporting evidence.