@xapp/contact-app@1.101.9
Booking & Contact Page for Form Widget
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe runtime function-construction path is a concrete dangerous capability, but the inspected source does not show that an attacker can control the fetched conditions or that the package uses it maliciously. No install lifecycle hook or confirmed attack behavior was found.
Decision evidence
public snapshot- The package exposes browser bundles and declares no install lifecycle hook; this risk is in runtime form-condition handling.
- The app fetches and parses widget configuration from its configured form service.
- The published bundle compiles configured field conditions with a function constructor and evaluates them against form context. Its identifier rewriting does not establish that expressions are safe.
- Inspected source shows no confirmed malicious condition, credential theft, or install-time attack; exploitation depends on an untrusted party being able to control the fetched configuration.
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 · L1Findings
Affected versions and remediation
This report applies to @xapp/contact-app@1.101.9.
See all versions of @xapp/contact-app for other recorded verdicts.
- Review the evidence and your use of @xapp/contact-app@1.101.9 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.