@xapp/form-widget@1.107.5
Form Widget
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe widget silently sends partial form answers on page close, before the visitor explicitly submits the form. This is suspicious runtime data collection, although sending completed form data to the widget’s configured service is consistent with the package’s purpose.
Decision evidence
public snapshot- On tab close, the widget merges its current form state and submits it as `partialData` with the abandonment reason `close_tab`.
- The partial-data beacon packages that object as a `partial_data` event and sends it to the configured widget API origin at `/cms/widget/events`.
- The package manifest exposes a form-widget entry point; the observed data collection occurs in the widget’s runtime form flow.
- The package is described as a form widget, so transmitting form answers to its configured service is related to its purpose.
- The beacon requires a configured widget key and is suppressed in demo mode.
- The package’s only lifecycle script is a build command; 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.107.5.
See all versions of @xapp/form-widget for other recorded verdicts.
- Review the evidence and your use of @xapp/form-widget@1.107.5 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.