@ujet/websdk-headless@6.9.0
A prebuilt infrastructure for communicating with your CCaaS servers!
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe scanner findings correspond to expected browser SDK networking, authentication, attachments, and bundled telemetry. Source inspection found no install-time execution or concrete malicious/exfiltration chain outside requested service functionality.
Decision evidence
public snapshot- Runtime config defaults to UJET API and bridge URLs.
- A user-triggered chat leave request sends the SDK auth token to its configured host.
- Chat file upload sends the caller-provided File to a server-provided upload URL.
- Bundle includes Bugsnag telemetry endpoint defaults.
- package.json has no lifecycle scripts or bin entrypoint.
- README requires the integrator to supply an authenticate callback before creating Client.
- Network and file operations implement the documented CCaaS chat/voice SDK workflow.
- No Node file/process APIs, persistence hooks, payload loading, or AI-agent control-surface writes were found.
Source & flagged code
4 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/index.jsView on unpkgA bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/index.jsView on unpkgFindings
Affected versions and remediation
This report applies to @ujet/websdk-headless@6.9.0.
See all versions of @ujet/websdk-headless for other recorded verdicts.
- Review the evidence and your use of @ujet/websdk-headless@6.9.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.