@xapp/contact-app@1.101.3
Booking & Contact Page for Form Widget
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe alleged hardcoded exfiltration resolves to a configurable form client authenticating to its supplied API destination, with tracking bound to that origin. Build commands and dynamic functions have identifiable package-related purposes, and inspected source does not establish malicious behavior.
Decision evidence
public snapshot- package.json has development scripts but no automatic install lifecycle hooks or runtime self-dependency.
- rollup.config.js runs a fixed Git branch query during builds.
- The form client receives its API URL and key from the supplied widget configuration and uses that key to authenticate requests to that URL.
- dist/xapp-contact-page.js derives the tracking destination from the configured API origin.
- The flagged dynamic function retrieves the global object; other dynamic functions evaluate configured form conditions.
- The exported contact page passes caller-supplied configuration to the form widget.
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 · L305Findings
Affected versions and remediation
This report applies to @xapp/contact-app@1.101.3.
See all versions of @xapp/contact-app for other recorded verdicts.
- Review the evidence and your use of @xapp/contact-app@1.101.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.