@xapp/contact-app@1.99.4
Booking & Contact Page for Form Widget
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe source matches a contact page library: it fetches configuration from XAPP endpoints, and third-party pixel tracking is initialized only when customer configuration supplies an ID. The scanner’s execution and Unicode flags resolve to build-time Git branch lookup, configured form conditions, and MUI date formatting; no attack chain was found.
Decision evidence
public snapshot- The package’s main and module entries are library bundles; its npm scripts contain no install lifecycle hook.
- The app fetches widget configuration from its configured XAPP form endpoint and uses XAPP API endpoints for the documented features.
- Meta and OpenAI pixels initialize from customer configuration; their events are page views and form leads, and initialization checks the browser’s Global Privacy Control signal.
- Dynamic Function calls compile configured form field and step conditions; no shell execution appears in the published bundle.
- The build configuration runs git rev-parse to read the branch for build replacement; this is build-time behavior.
- The bidi isolation characters flagged in the bundle occur in MUI date formatting; no review-directed override was identified.
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.99.4.
See all versions of @xapp/contact-app for other recorded verdicts.
- Review the evidence and your use of @xapp/contact-app@1.99.4 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.