@ujet/websdk-headless@6.20.0
A prebuilt infrastructure for communicating with your CCaaS servers!
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe scanner's exfiltration label is not supported by the inspected credential origin, connection configuration, and logging gates. Both entrypoint bundles show package-aligned communication behavior without a concrete malicious chain.
Decision evidence
public snapshot- package.json exposes two SDK bundles and declares no lifecycle scripts or runtime self-dependency.
- Authentication uses a caller-supplied callback token for the configured service connection.
- The connection defaults to the UJET bridge; custom host and bridge values come from caller options.
- Log forwarding requires an authentication response containing log_proxy_url, skips debug messages, and masks listed sensitive fields.
- The bundled Vonage client's Bugsnag reporting is disabled by default.
- The SDK handles authentication tokens, page URLs, network telemetry, and remote cobrowsing scripts; these capabilities warrant scrutiny but follow its communication features.
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.20.0.
See all versions of @ujet/websdk-headless for other recorded verdicts.
- Review the evidence and your use of @ujet/websdk-headless@6.20.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.