@xapp/contact-app@1.101.8
Booking & Contact Page for Form Widget
AI Security Review
scanned 19d ago · by lpm-firewall-aiThe flagged network and data handling are part of the contact widget: configuration uses XAPP endpoints, and partial form data is reported to the configured widget service when the widget closes. The manifest has no install lifecycle hook, and the inspected build command use is limited to reading the current Git branch.
Decision evidence
public snapshot- package.json defines the contact app entrypoints and has no preinstall, install, or postinstall hook.
- rollup.config.js uses a local Git command for build metadata and maps the package entrypoints to its bundles.
- The standalone bundle uses XAPP production endpoints, and src/App.tsx fetches widget configuration from the configured form service.
- The event tracker posts widget events to the configured widget service origin, gated by a widget key and demo mode.
- When a form widget closes, the app reports its entered form data as partial data to support the contact widget’s 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.8.
See all versions of @xapp/contact-app for other recorded verdicts.
- Review the evidence and your use of @xapp/contact-app@1.101.8 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.