@ujet/websdk-headless@6.7.0
A prebuilt infrastructure for communicating with your CCaaS servers!
AI Security Review
scanned 3mo ago · by lpm-firewall-aiDirect inspection found a packaged browser SDK with no lifecycle hooks and user-supplied authentication. Network and media behavior aligns with its documented chat and voice purpose; the scanner's exfiltration label is a false positive.
Decision evidence
public snapshot- Manifest exposes only bundled library entrypoints and declares no lifecycle scripts.
- README requires the integrator to supply an authenticate callback and token endpoint.
- Runtime networking is for the documented UJET communications API and explicit chat/call actions.
- Microphone access is requested through browser getUserMedia for voice-call functionality, not at install.
- Bundled code includes browser network, WebSocket, analytics, chat, and voice dependencies, which can look like exfiltration heuristically.
- A keepalive request sends the authenticated user's explicit chat-leave event to the configured UJET host.
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.7.0.
See all versions of @ujet/websdk-headless for other recorded verdicts.
- Review the evidence and your use of @ujet/websdk-headless@6.7.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.