@xapp/form-widget@1.105.2
Form Widget
AI Security Review
scanned 2mo ago · by lpm-firewall-aiStatic findings of network and environment primitives are explained by the shipped browser form widget and its dependencies. Source inspection found no concrete malicious behavior.
Decision evidence
public snapshot- The only lifecycle hook runs the package build command; there is no install, preinstall, or postinstall hook.
- The shipped browser entrypoint sends widget requests to the API URL and key supplied in its configuration.
- The hardcoded Xapp endpoint is used for address-autocomplete requests, not for credentials or harvested data.
- TrustedForm script loading rejects URLs whose origin is not api.trustedform.com.
- The widget sends configured form and tracking data at runtime, which is expected behavior for a form widget but should be assessed by the integrator for privacy.
Source & flagged code
5 flaggedSource contains bidi control or invisible Unicode characters associated with Trojan Source attacks.
dist/index.jsView on unpkg · L189A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
dist/index.jsView on unpkgFindings
Affected versions and remediation
This report applies to @xapp/form-widget@1.105.2.
See all versions of @xapp/form-widget for other recorded verdicts.
- Review the evidence and your use of @xapp/form-widget@1.105.2 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.