@xapp/contact-app@1.103.0
Booking & Contact Page for Form Widget
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe package is a contact page built around XAPP’s form widget, and the reviewed event traffic goes to the configured XAPP form service. Partial form data can be tracked when the widget closes, but this is tied to the form feature; the review found no unrelated collector, credential theft, or install-time behavior.
Decision evidence
public snapshot- The package describes itself as a booking and contact page for a form widget, with library entry points and no install lifecycle scripts.
- ContactPage renders the XAPP FormWidget as the page’s form, consistent with the package’s stated purpose.
- Form events are sent to the widget’s configured service URL; event tracking is skipped when no widget key is configured.
- The bundled form widget can send partial form data when a visitor closes it, as part of form event tracking.
- Default service endpoints are XAPP’s production and development hosts; build-time variables can override them.
- The bundler config invokes git to read the branch name during a build, but does not send it elsewhere.
- The bundle includes URLs and browser metadata, but the reviewed tracking sends them to the configured form service.
Source & flagged code
5 flaggedA single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/xapp-contact-page.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @xapp/contact-app@1.103.0.
See all versions of @xapp/contact-app for other recorded verdicts.
- Review the evidence and your use of @xapp/contact-app@1.103.0 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.