@ujet/websdk-headless@6.30.0
A prebuilt infrastructure for communicating with your CCaaS servers!
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe static credential-transfer signal resolves to ordinary SDK authentication and a chat-leave request sent to the configured service host. The manifest has no lifecycle scripts, and the inspected bundle locations show no unrelated credential collection or recipient.
Decision evidence
public snapshot- package.json exports the two distribution bundles and defines no lifecycle scripts.
- The chat-leave request requires an existing auth token and configured host, then posts to that host’s chat-leave route with the token as a bearer credential.
- Authentication obtains a token through the consumer’s authenticate callback and sends it to the UJET bridge/server authentication flow; the default API and bridge hosts are UJET endpoints.
- The CommonJS bundle shows the same configured-host chat-leave request and bearer header as the ES module.
- Early flagged bundle offsets contain private-field helper code, token-freshness logic, and event-manager setup, not a separate credential collection or transfer path.
- The flagged authorization header does transmit a token, but the source ties it to a chat-leave request at the configured SDK host and only sends when both the token and host exist.
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.30.0.
See all versions of @ujet/websdk-headless for other recorded verdicts.
- Review the evidence and your use of @ujet/websdk-headless@6.30.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.