@xapp/contact-app@1.94.5
Booking & Contact Page for Form Widget
AI Security Review
scanned 4mo ago · by lpm-firewall-aiThe flagged primitives are package-aligned browser widget behavior or build-time Git metadata lookup. Source inspection found no concrete malicious chain, lifecycle execution, data theft, persistence, or Trojan Source controls.
Decision evidence
public snapshot- `dist/index.es.js` evaluates configured form-step conditions with `new Function`.
- `src/App.tsx` fetches widget configuration and can load configured chat-widget assets.
- `src/utils/metaPixel.ts` injects Meta Pixel only for a validated configured pixel ID.
- `package.json` has no npm lifecycle hooks or `bin` entry.
- No Unicode bidi/invisible controls were found in the three distributed JavaScript bundles.
- `rollup.config.js` uses `execSync` only during builds to read the current Git branch.
- Authored source has no credential harvesting, filesystem access, shell execution, or exfiltration path.
- Network calls target declared XAPP services or optional Meta analytics and match contact-widget behavior.
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.5.
See all versions of @xapp/contact-app for other recorded verdicts.
- Review the evidence and your use of @xapp/contact-app@1.94.5 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.