@xapp/contact-app@1.94.3
Booking & Contact Page for Form Widget
AI Security Review
scanned 4mo ago · by lpm-firewall-aiThe scanner findings map to ordinary browser integrations and build-only Git metadata lookup. Direct source inspection found no install-time execution, exfiltration, destructive behavior, or malicious control-surface mutation.
Decision evidence
public snapshot- `src/App.tsx` fetches hosted widget configuration and conditionally loads the XAPP chat-widget script.
- `src/utils/metaPixel.ts` conditionally injects Meta Pixel after validating a configured numeric pixel ID.
- `package.json` has no preinstall, install, postinstall, prepare, or publish lifecycle hooks.
- `rollup.config.js` uses `execSync` only during builds to read the current Git branch.
- `src/services/partnerBranding.ts` posts only a partner code to the package-aligned GraphQL endpoint.
- No source file reads local files, harvests credentials, invokes shells at runtime, or writes persistence outside browser localStorage.
- Direct Unicode-control scan found no bidi/invisible control characters in the published bundles; the scanner Trojan Source signal is unsupported.
- Entrypoints export/render a React contact form; no import-time network, child-process, or payload execution is present.
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.94.3.
See all versions of @xapp/contact-app for other recorded verdicts.
- Review the evidence and your use of @xapp/contact-app@1.94.3 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.