@xapp/contact-app@1.100.0
Booking & Contact Page for Form Widget
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe flagged network and dynamic-script behavior is aligned with a browser contact form and explicitly configured analytics, while package installation has no lifecycle execution. The build-only Git command and bundled artifacts do not establish malicious behavior.
Decision evidence
public snapshot- The browser app conditionally initializes advertising pixels from its fetched widget configuration.
- The build configuration invokes Git only during an explicit build command, not package installation.
- The reviewed bundled entrypoints are ordinary JavaScript bundles with React imports and no install hook.
- package.json has no preinstall, install, postinstall, or self-dependency.
- Source fetches named XAPP configuration and partner-branding endpoints for the contact application.
- Pixel events are limited to page and lead events and are skipped when Global Privacy Control is enabled.
- No credential harvesting, filesystem access, shell execution at runtime, or persistence was found.
Source & flagged code
6 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.0.
See all versions of @xapp/contact-app for other recorded verdicts.
- Review the evidence and your use of @xapp/contact-app@1.100.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.