@xapp/contact-app@1.101.11
Booking & Contact Page for Form Widget
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe manifest has no install hook, and the inspected runtime requests serve contact-form, branding, and widget event functions at XAPP service endpoints. The scanner’s child_process hint is build-time Git branch lookup; the reviewed sources do not establish malicious behavior.
Decision evidence
public snapshot- package.json selects browser bundles and defines no install lifecycle hook.
- The widget sends keyed events to its tracking URL; its error reporter sends reports to an endpoint derived from the widget API URL, falling back to api.xapp.ai.
- The bundled form widget’s API calls use its configured bearer token, and the package’s production configuration points to XAPP API and form hosts.
- The contact page requests widget configuration from the configured form service, and partner branding is fetched through the configured GraphQL service.
- The build configuration uses child_process only to read the current Git branch, with a fallback if the command fails.
- Inspected network behavior is consistent with the contact and form widget functions; I found no source evidence of unrelated credential harvesting, exfiltration, or destructive behavior.
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.101.11.
See all versions of @xapp/contact-app for other recorded verdicts.
- Review the evidence and your use of @xapp/contact-app@1.101.11 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.