@xapp/contact-app@1.100.15
Booking & Contact Page for Form Widget
AI Security Review
scanned 1mo ago · by lpm-firewall-aiStatic inspection shows a React contact-page library with no install lifecycle, no secret harvesting, and network use limited to documented xapp API and form hosts. Build-time git lookup and in-page marketing pixels are product behavior, not a concrete attack chain.
Decision evidence
public snapshot- package.json has no preinstall, install, or postinstall hook; scripts are start, build, test, and eject only.
- Published entry points are React contact-page bundles: CommonJS dist/index.js, ESM dist/index.es.js, and browser UMD dist/xapp-contact-page.js.
- rollup.config.js calls execSync only to read the current git branch name during the library build.
- Source endpoints resolve to first-party xapp GraphQL and form hosts, overridable by build-time REACT_APP variables.
- Bundled form-widget code in dist uses new Function to evaluate configured field conditions after the page loads.
- The contact page can load Meta and similar marketing pixels and store UTM parameters in localStorage when the page runs.
Source & flagged code
7 flaggedThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
rollup.config.jsView on unpkgFindings
Affected versions and remediation
This report applies to @xapp/contact-app@1.100.15.
See all versions of @xapp/contact-app for other recorded verdicts.
- Review the evidence and your use of @xapp/contact-app@1.100.15 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.