@system-callifly/widget@0.1.0-beta.7
Callifly's embeddable voice/chat assistant widget — a framework-agnostic Web Component, usable via a <script> tag or npm install.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package manifest has no install lifecycle hooks, and the inspected network and dynamic-code behavior aligns with the widget’s stated chat and voice-call purpose. The scanner’s command-execution and exfiltration leads were not confirmed in the inspected entry bundle.
Decision evidence
public snapshot- The manifest points consumers to the widget’s UMD and ES module builds; its scripts are development, build, test and lint commands, with no install lifecycle hook.
- The chat client sends requests to api.vapi.ai using a configured bearer token, consistent with the widget’s stated voice/chat purpose.
- The Daily call SDK fetches its versioned call-machine bundle from c.daily.co and executes that bundle as part of loading call functionality.
- The UMD build includes dynamic execution of a fetched bundle, so the widget relies on remote code from its Daily call-service host.
- The package depends on browser-focused UI and document-processing libraries, matching the published embeddable widget purpose.
Source & flagged code
8 flaggedPackage source references child process execution.
dist/pdf-RgrI1mmZ.jsView on unpkg · L1715Package source references dynamic require/import behavior.
dist/pdf-RgrI1mmZ.jsView on unpkg · L6717Package source references a known benign dynamic code generation pattern.
dist/index-CAn7n2eC.jsView on unpkg · L490Findings
Affected versions and remediation
This report applies to @system-callifly/widget@0.1.0-beta.7.
See all versions of @system-callifly/widget for other recorded verdicts.
- Review the evidence and your use of @system-callifly/widget@0.1.0-beta.7 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.