@xapp/form-widget@1.110.0
Form Widget
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe widget automatically sends unfinished form answers to its configured events endpoint when the widget closes or the page unloads. Because the README documents attribution tracking but not this partial-answer collection, treat it as undisclosed runtime telemetry and warn users.
Decision evidence
public snapshot- Closing the widget can send current form values as `partialData` with a `widget_close` reason.
- A `beforeunload` handler sends partial form data with a `close_tab` reason.
- The data is sent as a `partial_data` event with browser and session metadata to `/cms/widget/events` on the configured API origin; the beacon uses the widget key.
- The README documents attribution parameter tracking but does not mention collection of unfinished form answers.
- The package is a multi-step form widget, so sending abandoned answers to its configured API could support form recovery or analytics.
- Beacon tracking is skipped in demo mode or when no widget key is configured.
- The `prepare` script runs the package’s Rollup build; no install-time data collection was identified.
Source & flagged code
4 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.110.0.
See all versions of @xapp/form-widget for other recorded verdicts.
- Review the evidence and your use of @xapp/form-widget@1.110.0 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.