comein-player-web@0.2.3
Customer-facing Web SDK built on top of the Comein player SDK.
AI Security Review
scanned 8d ago · by lpm-firewall-aiSource inspection shows a browser SDK with no install hook and a caller-supplied authentication flow directed to the Comein service. The scanner’s account-hijack finding was not corroborated by the inspected source.
Decision evidence
public snapshot- package.json exposes the browser bundles and contains no lifecycle script.
- The SDK requires caller-supplied roadshowId and userInfo; authentication can be disabled or skipped when userInfo already contains a token.
- The login flow sends userInfo to the fixed Comein channel-login endpoint and stores the returned session.
- The flagged CSS file contains player layout styling.
Source & flagged code
6 flagged · loading sourceBrowser source reuses an authenticated session to collect identity data and mutate account settings while reporting externally.
dist/index.umd.jsView on unpkg · L1The SDK requires caller-supplied roadshowId and userInfo; authentication can be disabled or skipped when userInfo already contains a token.
dist/index.umd.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to comein-player-web@0.2.3.
See all versions of comein-player-web for other recorded verdicts.
- Review the evidence and your use of comein-player-web@0.2.3 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.