@dori-ai/dori-side-widget@1.13.137
A modern, responsive chat widget built with React and Chakra UI, designed for seamless integration into any website. The widget provides an AI-powered chat experience with e-commerce capabilities, perfect for customer support and sales assistance.
AI Security Review
scanned 22d ago · by lpm-firewall-aiThe entrypoint and inspected bundle implement a storefront chat widget, with customer-token retrieval tied to a same-origin route and the presence of a customer ID. The tracking and chat requests are package-aligned, and the inspected source does not substantiate the scanner’s account-hijack claim.
Decision evidence
public snapshot- package.json identifies dist/widget.js as the entrypoint and contains no lifecycle scripts.
- The entrypoint imports and initializes the main widget bundle when loaded.
- The widget fetches a customer token only when DORI_CUSTOMER_ID is present, using the same-origin customer-token route.
- The chat flow sends the message and optional customer context to the widget’s run-assistant API route.
- The tracking function sends ecommerce identifiers to the widget’s product-view tracking route; no unrelated recipient or account-setting mutation was identified.
- Offline analysis reports the compressed widget expands to the inspected entrypoint and lists no analysis limitations.
Source & flagged code
6 flaggedPackage source references dynamic require/import behavior.
dist/widget.jsView on unpkg · L1The entrypoint imports and initializes the main widget bundle when loaded.
dist/widget.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @dori-ai/dori-side-widget@1.13.137.
See all versions of @dori-ai/dori-side-widget for other recorded verdicts.
- Review the evidence and your use of @dori-ai/dori-side-widget@1.13.137 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.