@ujet/websdk-headless@6.19.1
A prebuilt infrastructure for communicating with your CCaaS servers!
AI Security Review
scanned 1mo ago · by lpm-firewall-aiInspected metadata and runtime behavior are consistent with a browser customer-support SDK. No concrete malicious behavior was found, and configurable authentication uses caller-supplied credentials.
Decision evidence
public snapshot- package.json exports browser SDK bundles and declares no lifecycle scripts or dependencies.
- Both runtime entrypoints obtain authentication tokens from a caller-provided callback.
- Service configuration uses caller options and a default UJET bridge; authenticated chat requests target the configured service.
- Browser storage uses the ujet: prefix for SDK state.
- Co-browsing session restoration requires the caller's enabled option and stored session state.
Source & flagged code
3 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.19.1.
See all versions of @ujet/websdk-headless for other recorded verdicts.
- Review the evidence and your use of @ujet/websdk-headless@6.19.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.