@xapp/contact-app@1.100.5
Booking & Contact Page for Form Widget
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe source implements a contact page that fetches its widget configuration from XAPP services and can load customer-configured conversion pixels. The scanner’s Unicode and execution indicators are consistent with date-picker text handling and configurable form conditions; no malicious behavior was established.
Decision evidence
public snapshot- The package describes a booking and contact page and exports a ContactPage component.
- Its npm scripts are start, build, test, and eject; none is an install lifecycle hook.
- The app fetches widget configuration from its configured XAPP form service using the widget key.
- Production and development endpoints are XAPP services; partner branding uses the configured GraphQL endpoint.
- Meta and OpenAI pixels are initialized only when their IDs are present in customer configuration.
- The external pixel SDK scripts are loaded from their respective vendor hosts.
- The bundled form widget evaluates configured field and step conditions with new Function; this supports configurable forms but is a dynamic-code capability.
- The widget uses network requests and tracking data as part of its contact-form and attribution functionality.
- A Unicode isolate pair appears in bundled date-picker code for right-to-left text; it is not evidence of concealed control flow.
Source & flagged code
5 flaggedSource contains bidi control or invisible Unicode characters associated with Trojan Source attacks.
dist/xapp-contact-page.jsView on unpkg · L193Findings
Affected versions and remediation
This report applies to @xapp/contact-app@1.100.5.
See all versions of @xapp/contact-app for other recorded verdicts.
- Review the evidence and your use of @xapp/contact-app@1.100.5 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.