comein-player-web@0.2.2
Customer-facing Web SDK built on top of the Comein player SDK.
AI Security Review
scanned 10d ago · by lpm-firewall-aiSource inspection found no install-time execution or concrete account-hijacking behavior. The token-bearing telemetry is a sensitive implementation choice, but the inspected path is Comein-aligned and gated to Comein-domain pages, so it does not establish a malicious attack surface.
Decision evidence
public snapshot- The manifest publishes the player bundles directly and defines no lifecycle scripts.
- Player creation passes the caller’s options to authentication; the default login bases are Comein production and test services, and the supplied user information goes to the Comein login route.
- The logger can include the caller’s user identifier and session token in reports. Its reporting transport uses the Comein logging project and temporary credentials from Comein, and uploads are gated to Comein-domain pages.
- The stylesheet contains player layout and presentation rules.
- The logger places the session token in telemetry records, which is sensitive data handling even though the reporting path is Comein-aligned and domain-gated.
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 · L1Player creation passes the caller’s options to authentication; the default login bases are Comein production and test services, and the supplied user information goes to the Comein login route.
Findings
Affected versions and remediation
This report applies to comein-player-web@0.2.2.
See all versions of comein-player-web for other recorded verdicts.
- Review the evidence and your use of comein-player-web@0.2.2 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.