@xapp/form-widget@1.113.1
Form Widget
AI Security Review
scanned 19d ago · by lpm-firewall-aiThe bundles transmit partial form data on widget close, but route the event to the configured service origin and require its widget key. This is consistent with the widget’s event-tracking behavior and does not establish a concrete attack surface.
Decision evidence
public snapshot- package.json’s prepare hook runs the build script.
- The bundles include entered form data in a partial-data event when the widget closes and data exists.
- Event requests require a configured widget key and post to the configured URL’s own origin at /cms/widget/events.
- The standalone bundle uses the same configured-origin event route.
- The event recipient is derived from the widget’s configured service URL; the inspected source does not establish an unrelated hardcoded receiver or another concrete attack behavior.
Source & flagged code
5 flaggedA single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/index.jsView on unpkg · L1Package source references a known benign dynamic code generation pattern.
dist/index.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @xapp/form-widget@1.113.1.
See all versions of @xapp/form-widget for other recorded verdicts.
- Review the evidence and your use of @xapp/form-widget@1.113.1 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.